Content
65%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.
A well-structured, largely actionable body with excellent progressive disclosure — verified one-level-deep references and executable commands for every script. Weaknesses are moderate padding (redundant sections and format-choice explanations Claude already knows) and the batch workflow's missing validation steps, which the rubric caps at 3.
Suggestions
Add explicit validation steps to the batch workflow: specify the gene_list.txt input format, check the output for unmatched or invalid gene symbols, and show how to inspect and retry failures before using results.
Trim redundant or background sections — the Resources listing duplicates earlier script/reference descriptions, and the Data Formats guidance (choose JSON vs XML vs FASTA) explains concepts Claude already knows; keep only NCBI-specific format options.
Collapse or cut the Overview and When to Use sections, which largely restate the frontmatter description and general NCBI background.
| Dimension | Reasoning | Score |
|---|---|---|
Conciseness | Mostly efficient (commands, query patterns, error codes), but several padded sections: the Overview paragraph describing NCBI Gene, a Data Formats section explaining JSON/XML/FASTA tradeoffs Claude already knows, a "When to Use" section restating the description, and a Resources section duplicating the script/reference listings already given. Fits anchor 3 ("some unnecessary explanation or could be tightened"), not 4 whose over-explanation would be only minor. | 3 / 5 |
Actionability | Copy-paste-ready bash commands for each script with realistic examples ("--search \"BRCA1\" --organism \"human\""), concrete error codes and rate limits. Not 5: the batch workflow never specifies the gene_list.txt input format and no expected output is shown — minor gaps matching anchor 4. | 4 / 5 |
Workflow Clarity | Sequences are clearly listed per workflow, but the batch lookup workflow — explicitly a batch operation — has no validation or verification step (no check for unmatched symbols, no inspect-and-retry loop); "Retry failed requests with exponential backoff" is generic API guidance, not an embedded checkpoint. Per the rubric's cap for batch operations without validation, workflow clarity is capped at 3. | 3 / 5 |
Progressive Disclosure | Clear overview with real, one-level-deep references (references/api_reference.md, references/common_workflows.md), each described with its purpose plus explicit navigation guidance ("Search these references when needing specific API endpoint details..."), and all referenced scripts exist in the bundle. Matches anchor 5: content appropriately split and easy to navigate. | 5 / 5 |
Total | 15 / 20 Passed |