Get Curations for Many Genes

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

Annotations already declare readOnly, openWorld, idempotent, and not destructive. The description adds that the call still succeeds even with unresolvable inputs (returned in 'unresolved') and each result mirrors get_gene_curations, which are useful behavioral details beyond the 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?

Two succinct sentences that front-load the primary purpose and efficiently cover usage, parameters, and behavior with no wasted words.

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 the output schema exists (so return values are covered), the description explains batch behavior, partial failures, parameter usage, and relation to the singular form. It is fairly complete for a batch tool with three parameters, though the genes parameter could be more detailed.

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 low (33%); only response_mode has a brief description in the schema. The description adds meaning for limit_per_gene (caps diseases per gene) and response_mode (widens detail), but does not elaborate on the genes parameter format or constraints beyond 'gene symbols or HGNC ids'. This provides some but not full compensation.

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 is a batch form of get_gene_curations, taking a list of gene symbols or HGNC ids (max 20) to retrieve disease assertions for multiple genes. It distinguishes itself from the singular sibling get_gene_curations.

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 when to use this batch tool (for multiple genes), mentions the max of 20, and explains how unresolved inputs are handled. However, it does not explicitly state when not to use it (e.g., when you need only one gene).

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