batch_get_gene_xrefs

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

With no annotations, description discloses parallelism, limit of 50 loci, result structure, and error handling. Could mention performance or side effects but sufficient.

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 key info, no wasted words. Efficient and clear.

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?

Given complexity (batch, parallel, error handling) and presence of output schema, description covers main aspects. Could detail output schema further but not needed when schema exists.

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% so baseline 3. Description adds context: loci identifiers, organism flexibility, and clarifies error vs success mapping. Adds value beyond 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?

Clearly states it is a batch variant of get_gene_xrefs, performs parallel lookups for up to 50 loci, and describes the output shape. Distinguishes from the single-locus sibling.

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?

Indicates usage for multiple loci via 'batch variant' and 'fans out...in parallel'. Implicitly when not to use (single locus) via sibling naming, but lacks explicit alternatives or exclusions.

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