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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so the safety profile is well covered. The description adds provenance ('itis.gov, USGS public data') and the list of populated fields, but it does not disclose behavior on invalid TSNs or result limits, though the output schema reduces the need for return-value explanation.

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 a single front-loaded sentence stating the action, input, and output contents without filler. The field enumeration is dense but every element adds meaning.

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?

For a one-parameter, read-only lookup with an output schema and strong annotations, the description is nearly sufficient. The inaccurate sibling tool names in the parameter description create a real caller-facing gap, and there is no fallback guidance for users who do not already have a TSN.

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 coverage is 100%, and the tsn parameter description goes beyond the schema with a definition ('unique numeric identifier'), a concrete example ('180543' for Ursus arctos), and guidance to obtain the TSN from search tools. The slight inaccuracy in the referenced sibling names prevents a higher score.

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 uses a specific verb ('Get'), names the resource ('full taxonomic record for a species by its ITIS TSN'), and enumerates the returned fields: accepted name, author, kingdom, rank, parent taxon, validity status, synonyms, and common names. This clearly distinguishes it from the sibling search tools, which find taxa rather than retrieve the full record.

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 parameter schema provides a usable path: obtain a TSN from the search tools before calling this tool. However, the referenced tool names ('itistaxonomy.search_scientific_name' and 'itistaxonomy.search_common_name') do not match the actual siblings ('science.itistaxonomy.search_scientific' and 'science.itistaxonomy.search_common'), and the description does not explicitly state when to prefer this tool over the search alternatives.

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