Browse ICD-11 Hierarchy

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint false, so the safety profile is known. The description adds no new behavioral details beyond what the schema already states about direction values returning ancestors or subcategories. It does not contradict the annotations.

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 logically structured but somewhat redundant: the bullet list restates the opening sentence, and the final sentence repeats the schema text. It could be condensed to two sentences without losing meaning, so it's not optimally 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?

For a simple navigation tool with only two parameters, an output schema, and strong annotations, the description covers the essential purpose and usage adequately. No critical information appears missing, though it could mention output behavior if not already covered by the output schema.

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 the baseline is 3. The description's explanation of 'parents' and 'children' largely duplicates the schema's parameter descriptions, providing no additional semantics beyond what's already structured.

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 explicitly states it navigates the ICD-11 hierarchy to find parent or child entities. It clearly distinguishes itself from sibling tools like icd11_search or icd11_lookup by focusing on hierarchical relationships. The bullet list further clarifies the specific use cases.

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 provides explicit use cases: finding broader categories, finding subtypes, and understanding classification structure. It does not explicitly name alternative tools or say when not to use it, but the context is clear enough that an agent would understand when to select this tool.

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