Get Gene Info

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds valuable behavioral context: it auto-indexes the gene entity into the session knowledge graph (a side effect beyond read-only). No contradictions.

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 two sentences, front-loaded with purpose, no wasted words. Every sentence provides value (purpose and data types; auto-indexing side effect).

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?

No output schema, but the description lists return data types (symbol, full name, etc.). Annotations cover behavioral aspects. Complexity is moderate; the description is sufficiently complete for a retrieval tool, though explicit return format could help.

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 good parameter descriptions. The description adds that gene_symbol is an HGNC symbol and specifies the default organism, but these are already in the schema. It does not significantly enhance understanding beyond the 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 specifies a specific verb ('Retrieve') and resource ('gene information from NCBI Gene') and lists concrete data types. It distinguishes from siblings like 'get_protein_info' by focusing on NCBI Gene and auto-indexing into the session knowledge graph.

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 implies use for gene information retrieval but does not explicitly state when to use this tool vs. alternatives (e.g., 'find_protein' or 'get_protein_info'). No exclusions or comparison provided.

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