gene_info_fetch

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

Discloses rate limiting, precedence rules (gene_id over gene_symbol), caching behavior, TTL inheritance, and structured output format. No annotations exist, so description carries full burden and does so thoroughly.

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?

Well-organized with clear sections (Args, Returns, Examples, Notes). Every sentence adds value; no redundancy. Front-loaded with purpose.

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?

Covers all aspects: input parameters, output schema, examples, and behavioral notes. No missing information for a tool with this complexity and no annotations.

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 0%, but the description's Args section explains each parameter with defaults, examples, and precedence. Fully compensates for lack of schema descriptions.

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 'Fetch comprehensive gene information from NCBI Gene database' with specific verb and resource. Differentiates from sibling tools like entrez_fetch by being a specialized wrapper for gene records with structured output.

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: 'Provide either gene_symbol or gene_id', organism disambiguation, rate limits, and caching. Lacks explicit when-to-use vs alternatives, but examples and purpose imply usage for gene info.

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