Resolve Gene Symbols (Batch)

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

Discloses the resolution cascade, individual miss behavior (marked unresolved/obsolete), and returned counts. No contradictions with annotations (readOnlyHint, idempotentHint, etc.).

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 focused sentences with no redundancy. Front-loaded with purpose. Highly efficient.

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?

Explains return values (per-query results + counts) despite no output schema. Could briefly describe what each response_mode yields, but overall sufficiently complete for a batch read tool.

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 has 100% coverage, but description adds significant context: explains the cascade, batch safety, and that response_mode controls verbosity. Mentions signature for clarity.

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?

Description clearly states it resolves a batch of gene symbols/HGNC IDs (max 200) with the same cascade as resolve_symbol. It specifies per-query results and counts, distinguishing it from sibling tools like resolve_symbol.

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?

Provides clear context for batch usage (max 200) and behavior on misses/withdrawals. Implicitly suggests using resolve_symbol for single queries, but lacks an explicit when-not statement.

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