Get Disease Descendants

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

Annotations already declare readOnlyHint, destructiveHint, idempotentHint, openWorldHint. The description adds details on pagination block structure, truncation behavior, next_offset, next_commands, and response_mode verbosity. 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: purpose + pagination, sibling distinction, signature. Each sentence is necessary and front-loaded. No fluff.

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?

With 4 fully described parameters, output schema, and rich annotations, the description is complete. It covers pagination, truncation, sibling alternative, and parameter signature. No gaps for a tool of this complexity.

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%, so baseline is 3. The description adds value by explaining pagination output context (truncation, next_offset) which helps understand limit/offset behavior. It repeats some schema info but the pagination explanation is useful.

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 specifies the verb 'Return', the resource 'transitive descendants of an Orphanet disorder', and the method 'via precomputed closure'. It also distinguishes from the sibling tool get_disease_classification, which returns only immediate children.

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?

Explicitly states when to use this tool and when to use get_disease_classification instead. Provides context on pagination and parameter signature. Lacks a comprehensive 'when not to use' but the guidance is clear.

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