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

Annotations declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, and destructiveHint=false, which convey a safe, read-only, idempotent operation. However, the description adds no additional behavioral context (e.g., what data is returned, whether external APIs are queried, or any limitations). It does not contradict the annotations but also doesn't enhance them.

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 concise at four words, but it is under-specified rather than appropriately scoped. It lacks a verb and fails to convey essential purpose information. While not verbose, it sacrifices clarity for brevity, making it less effective than a slightly longer but more informative description.

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?

The tool has one parameter and an output schema, but the description provides no context about what taxonomy information is returned, how the species parameter should be formatted, or what taxonomic database is used. The description is too sparse to be considered complete even for a simple single-parameter tool, and the output schema is not visible to the agent in this context.

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 0%, so the description must compensate but does not. The word 'Species' in the description weakly hints at the 'species' parameter, but the schema already provides the parameter name, type, and examples ('human', '9606'). The description adds no clarification on accepted formats or meaning beyond the schema, leaving the agent to infer from the bare examples.

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 'Species taxonomy info' is a vague noun phrase with no verb. It does not state what operation is performed (e.g., lookup, search, retrieve) and does not distinguish the tool from siblings like 'metadata' or 'entity_profile' which could also provide taxonomic data.

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?

There is no guidance on when to use this tool versus alternatives, no context on prerequisites, and no mention of acceptable input formats (e.g., common name vs. taxonomy ID). The description merely states the topic, leaving the agent to guess the intended use case.

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