taxonomy_summary

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It describes the output fields but does not disclose behavioral traits such as that it is a read-only operation, error handling for invalid taxon inputs, or any rate limits. The description is adequate but incomplete for full transparency.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is extremely concise, consisting of a single sentence followed by a parameter explanation. The purpose is front-loaded, and every sentence adds value. No wasted words.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has only one parameter and an output schema (not shown), the description provides sufficient context about the input and output. It lists the categories of returned data, which is helpful. Lacks details on error handling or edge cases, but the presence of an output schema reduces the burden. Nearly complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has 0% description coverage, but the description compensates thoroughly. It explains the parameter 'taxon' accepts both scientific names (with examples like 'human', 'Bacteria') and NCBI tax IDs, adding crucial semantic context beyond the schema's type definition.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Get taxonomy metadata for a taxon' and lists the types of data returned (lineage, rank, scientific name, common names, child taxa). It specifies the verb 'Get' and the resource 'taxon', making it distinct from siblings like 'taxonomy_download' which implies bulk data retrieval.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for retrieving taxonomy metadata but does not explicitly state when to use this tool versus alternatives such as 'genome_summary_by_taxon' or 'taxonomy_download'. No guidelines for when not to use it are provided, relying on the agent to infer from the purpose.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.