get_taxon_summary

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

No annotations are provided, so the description carries the full disclosure burden. The 'Get' prefix and summary framing imply a read-only aggregation, and it discloses what categories of data are returned, but it says nothing about permissions, rate limits, or whether counts are cached/approximate.

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?

Two sentences, front-loaded with the core action and returned fields, with no redundant restatement of the name. The closing benefits sentence is mildly generic but still adds usage signal.

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?

With no output schema, the description appropriately enumerates the return contents (genome counts, species counts, child taxa, description), which is what an agent needs to decide to call it. The absence of annotations leaves permission/safety behavior unspecified, a minor gap for a read-style tool.

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?

Schema description coverage is 100% and the schema already documents the single 'name' parameter with concrete taxon examples (Bacillota, Gammaproteobacteria, etc.). The description adds no format or level-specific semantics beyond what the schema provides, so the baseline of 3 applies.

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?

States a specific verb ('Get') and resource ('summary of a taxonomic group') and enumerates the returned content (genome counts, species counts, child taxa, description). It does not explicitly contrast itself with close siblings like get_taxonomy or get_children, so an agent must infer the distinction from the 'comprehensive summary' framing.

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 second sentence gives a reason to call it ('understanding the diversity and composition of any taxonomic level'), which implies usage but names no alternatives and provides no when-not conditions. There is no guidance on choosing it over get_taxonomy or get_children.

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