get_gene_pathways

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

No annotations provided; description only states function without disclosing behavioral traits such as read-only nature, error handling, or rate limits.

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?

Single, concise sentence with no unnecessary words; information is front-loaded.

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?

For a simple one-parameter tool, description covers core purpose but lacks details about return format or behavior when gene is not found.

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?

Parameter 'gene' has good schema description coverage (100%). Description adds context that gene is queried against KEGG pathways, which is useful but minimal beyond 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?

Description clearly states verb 'Find', resource 'KEGG pathways', and scope 'a gene'. Distinguishes from siblings like get_kegg_pathway which likely retrieves a specific pathway.

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?

Implied usage for gene-to-pathway lookup but no explicit when-not-to-use or mention of alternatives like get_kegg_pathway or search_kegg_pathway.

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