Content
75%Weight 40%Scale 1-5Reviews the quality of instructions and guidance provided to agents. Good implementation is clear, handles edge cases, and produces reliable results.
The content is a well-structured, actionable regulatory-variant workflow: phased sequence, concrete tool parameters with gotchas, fallbacks, examples, and limitations. Its main gap is the absence of an actual executable Python code block to back the 'compute, don't describe' directive, plus no explicit gated validation checkpoints.
Suggestions
Add at least one concrete, copy-paste Python example (e.g., calling gwas_search_associations via the ToolUniverse client and filtering hits with pandas at p<5e-8) to make the 'COMPUTE, DON'T DESCRIBE' directive executable.
Insert explicit validation checkpoints in the workflow (e.g., after Phase 0 'confirm rsID resolves and nearest gene is non-null before querying eQTL') to lift workflow_clarity toward 5.
Tighten the 'Non-Coding Variant Impact Reasoning' and 'Functional Impact Synthesis' sections, which restate overlapping histone-mark and convergence criteria, to reduce token cost.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is efficient and domain-specific (tool params, reasoning tips, fallbacks) with little generic padding; the four-question and synthesis sections restate some interpretation heuristics that could be tightened, keeping it just below a lean 5. | 4 / 5 |
Actionability | Concrete tool names with exact params and gotchas ('EnsemblVEP_annotate_rsid (param is variant_id, not rsid)', 'p_value=5e-8') plus step-by-step example workflows make it mostly executable; it stops short of a 5 only because the 'COMPUTE, DON'T DESCRIBE' directive is never backed by an actual runnable code block. | 4 / 5 |
Workflow Clarity | A clear Phase 0–6 sequence with a diagram and reactive Fallback Strategies gives a strong, mostly-checkpointed flow; it lacks explicit gated validation steps ('verify X before proceeding'), so it does not reach the checklist/feedback-loop richness of a 5. | 4 / 5 |
Progressive Disclosure | No bundle files exist, so all content is one self-contained file with well-signaled section headers and no nested references — good structure with only minor inlining of tool reference detail that could live in a separate file. | 4 / 5 |
Total | 16 / 20 Passed |