Resolve Gene Symbols (Batch)

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

Annotations already provide safety profile (readOnly, idempotent, non-destructive). The description adds useful behavioral details: batch limit, error handling (failures mark as unresolved), per-query results with counts, and cascade logic. No contradiction with annotations.

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?

Three sentences, front-loaded with main purpose. Every sentence adds information. No fluff.

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 batch complexity and presence of output schema (return values not needed), the description covers error behavior, batch limit, comparison to singular tool, and parameter options. Could mention output structure briefly but not essential.

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% with descriptions, and the description adds value beyond schema: explains the cascade behavior for resolution and the error handling. The signature mention reinforces parameter usage.

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 it resolves a batch of gene symbols/HGNC ids, specifies the max batch size (200), and distinguishes from the sibling tool 'resolve_symbol' by being batch and noting the same cascade approach.

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 explains that individual failures don't fail the batch, implying when to use this over singular resolve_symbol. It doesn't explicitly list alternatives but context from sibling tools makes it clear. Could be more explicit about when not to use.

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