Get HPO Term Ancestors

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. Description adds significant behavioral context: precomputed closure, pagination block structure, next_offset mechanism for walking limits. 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?

Three sentences, front-loaded with main action. Second sentence addresses edge case (truncation). Third sentence gives alternative and signature. No redundant words.

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?

Complete for a read-only paginated tool with output schema. Covers purpose, pagination, truncation, sibling alternative, and parameter signature. No missing critical context.

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%, so baseline 3. Description adds a signature line summarizing parameters and explains pagination implications for offset/limit. Enriches understanding beyond schema, but does not detail each parameter further.

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?

Explicitly states 'Return all transitive is_a ancestors' – verb and resource are specific. Distinguishes from sibling get_term_parents by noting it returns all ancestors vs. immediate parents.

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 explicit alternative: 'Use get_term_parents for only the immediate parents.' Also explains pagination behavior and how to handle truncated results, guiding sequential paging.

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