get_hpo_term

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

The description lacks annotations, so it carries the full burden. It states the tool retrieves information but does not disclose what 'detailed information' includes, expected side effects (likely none), or response format. For a read-only retrieval, it is minimally adequate but not transparent.

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 a single sentence with no wasted words. It is front-loaded with the action. Could be slightly more informative without increasing length, but it is appropriately concise.

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 tool's simplicity (1 parameter, no output schema), the description is mostly complete but does not mention return value or confirm read-only nature. For a simple retrieve-by-ID tool, it is adequate but not thorough.

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 100% (the 'id' parameter is described in the schema). The description adds no new meaning beyond the schema, just restates 'by its ID'. Baseline is 3, and no extra value is provided.

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 the action 'Get' and the resource 'detailed information about a specific HPO term by its ID'. It uniquely identifies the tool's purpose among siblings like 'search_hpo_terms' and 'get_all_hpo_terms'.

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 usage when one has a specific HPO term ID and wants detailed info, but it does not explicitly contrast with siblings like 'batch_get_hpo_terms' or 'search_hpo_terms'. No when-not-to-use guidance is provided.

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