biothings_get_taxons

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 states it retrieves information for multiple taxa in a single request and gives format examples. However, it does not disclose error handling (e.g., partial failures), rate limits, authentication, or what happens with invalid IDs, leaving gaps in behavioral understanding.

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 front-loaded with the main purpose and includes helpful examples. At 10 lines, it is slightly verbose but each sentence adds value. It is well-structured and easy to scan.

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?

An output schema exists, so return values are covered. The description explains the required parameter well but omits details about optional parameters (email, fields) and their defaults. For a simple fetch tool, it is moderately complete but could be improved.

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 schema has 3 parameters (email, fields, taxon_ids) with 0% description coverage. The description adds meaning to 'taxon_ids' by specifying comma-separated format and examples, but does not explain 'email' or 'fields'. Thus, it partially compensates for the schema's lack of descriptions.

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 'Fetch multiple taxa by a comma-separated list of NCBI IDs or scientific names,' specifying the action, resource, and input format. It distinguishes itself from siblings like 'biothings_get_taxon' (singular) and 'biothings_query_taxons' (likely query-based).

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 provides explicit input format and examples, making it clear when to use the tool (fetching multiple taxa by IDs/names). It does not explicitly state when not to use it or mention alternatives, but the sibling tool names imply singular vs plural and fetch vs query distinctions.

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