biothings_query_many_taxons

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

No annotations are provided, so the description must carry the full burden. It only states the tool performs multiple queries and gives examples, but does not disclose behavioral traits such as query limits, case sensitivity, partial match handling, or whether it is read-only. This lacks sufficient transparency for a batch query tool.

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 moderately sized and well-structured with a brief intro and bullet points. It is front-loaded with the main purpose. Some sentences could be trimmed, but overall it is clear 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?

With 4 parameters, no annotations, and an output schema, the description covers major usage patterns but omits details on query_list format and email parameter. The complexity warrants more complete guidance, especially for a tool that expects a list-like input as a string.

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 compensates by explaining the usage of scopes and fields parameters with concrete examples. However, the email parameter is not mentioned, and the query_list parameter format (JSON array as string) is not clarified. Still, it adds significant meaning beyond the bare schema.

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 performs batch queries for taxa using multiple terms, with specific examples of scientific and common names. It distinguishes itself from sibling tools like biothings_get_taxon by emphasizing batch capability and multiple query types.

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 usage scenarios: multiple query types, field scoping, and result filtering. It implies use for batch queries but does not explicitly mention when not to use or compare to biothings_query_taxons, though sibling names provide some context.

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