Content
63%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 body is a well-organized, domain-rich reference with a clear phased workflow and concrete tool documentation. Its main weaknesses are token duplication (tool details appear twice), an internal p-value contradiction, missing ToolUniverse setup context for the examples, and no progressive disclosure of the API-reference material into bundle files.
Suggestions
Eliminate the duplication between the per-phase tool sections and the 'Tool Quick Reference' table — keep one (the table) and reference it from the phases, cutting roughly a quarter of the body's tokens.
Fix the p-value contradiction: Phase 5 correctly states the tool returns 'no log-rank p-value', but the Quick Reference says 'Kaplan-Meier donor array + pValue' and Workflow 1 step 3 promises a 'p-value' — align all three to Phase 5's accurate account.
Show the ToolUniverse setup (e.g., 'import tooluniverse as tu') once so the 'tu.tools.*' examples are copy-paste runnable, and move the per-tool API details and the 'Programmatic Access' section into a references/ file for progressive disclosure.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | The body is dense with domain-specific data Claude doesn't know (tool params, return shapes, NCIt codes), but it is noticeably redundant: every tool's params and returns appear both in the phase sections and again in the 'Tool Quick Reference' table, the example workflows re-state phase-level calls, and a 'verified 2026-09-21' date sits in a code comment. Mostly efficient but needs tightening matches the 3 anchor. | 3 / 5 |
Actionability | Concrete tool signatures with parameter types, return-shape documentation, realistic Python examples, and a bulk GDC API script make the guidance mostly executable. Two gaps hold it below 5: the examples use 'tu.tools.*' with no setup/import shown anywhere, and the Tool Quick Reference and Workflow 1 claim a 'pValue'/'p-value' that Phase 5 explicitly says the tool does not return. | 4 / 5 |
Workflow Clarity | A clear six-phase sequence with an ASCII overview, a confirm-first checkpoint ('LOOK UP DON'T GUESS', 'confirm a project exists... before deeper queries'), example workflows, and a limitations section. Checkpoints are present but implicit rather than explicit validate-and-recover loops, matching the 4 anchor; no destructive/batch cap applies since all operations are read-only queries. | 4 / 5 |
Progressive Disclosure | No bundle files exist (references/, scripts/, assets/ are absent), so all material — per-tool API reference, reasoning framework, and programmatic bulk access — is inlined in a ~330-line single file. Sections are well-organized with clear headers, but API-reference content that would naturally live in a separate file is inline, matching the 3 anchor. | 3 / 5 |
Total | 14 / 20 Passed |