get_go_term

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

No annotations are provided, so the description carries the disclosure burden. 'Fetch' and the Returns section imply a safe read-only lookup with no side effects, but it does not state behavior on invalid/nonexistent GO IDs or any rate limits. Adequate but thin for a tool with zero annotation coverage.

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?

Front-loaded one-line purpose followed by compact Args/Returns sections; no wasted prose. The Returns block partially duplicates the output schema, but it is short and harmless.

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 single-parameter read lookup with an output schema, the definition covers purpose, argument format, and anticipated return content. The main gap is the absence of any usage routing against the numerous sibling tools, which is a moderate shortfall rather than a critical one.

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% and the schema gives only a bare 'Go Id' string, so the description must compensate. It does so by naming the parameter, specifying its meaning ('Gene Ontology identifier'), and giving a concrete format example ('GO:0006915'). This meaningfully exceeds 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?

States a specific verb ('Fetch') and resource ('Gene Ontology (GO) term ID') with the kind of data returned (metadata and functional definition). This clearly separates it from the many gene/pathway/publication siblings, which operate on different resources.

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?

There is no guidance on when to use this tool versus alternatives such as get_pathway_details or annotate_function, and no mention of prerequisites or when it should not be used. The agent must infer usage purely from the resource name.

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