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

Annotations already state readOnlyHint, openWorldHint, idempotentHint, and destructiveHint false, so the safety profile is covered. The description adds the top-level categories scope and the 28-chapter count but no additional behavioral details such as ordering, pagination, or response variations; this is adequate but not rich.

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 short, front-loaded, and scannable with a lead sentence and three bullet uses. It is mostly efficient, though the final clause about covering all areas of medicine is broad and adds marginal value.

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-optional-parameter, read-only listing tool with a rich output schema and full annotations, the description covers what the tool does, why an agent would use it, and what scope to expect. Nothing critical is missing.

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 language parameter is fully documented in the input schema, including default, enum, and official-translation behavior. The tool description adds nothing about parameters, so the baseline of 3 is appropriate.

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 opens with a clear verb and resource, 'List all ICD-11 chapters (top-level categories)', and the bullet list explains what this is for. It does not explicitly contrast itself with sibling tools such as icd11_hierarchy or icd11_search, so it falls short of full differentiation.

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 bullet list provides concrete use cases: get an overview, find which chapter covers a body system or condition type, and navigate to specific disease categories. It omits explicit exclusions or when-not-to-use guidance compared with sibling tools, giving clear context but no alternatives.

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