Capítulo da CID-10

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the safety profile is covered. The description adds meaningful behavioral context by specifying that the tool returns a chapter's constituent groups and includes an example showing the output structure, which goes beyond 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 concise, front-loads the core purpose, and uses a clear bulleted list for usage scenarios. The example is somewhat lengthy but adds valuable concreteness. It could be tightened slightly by removing the redundant 'Provide a chapter number (1-22)' since the schema already covers this.

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?

The tool is simple with one parameter and an output schema available, so the description does not need to detail return fields. It clearly communicates what the tool does and its primary usage contexts. This is sufficient for an agent to select and invoke the tool correctly.

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?

The input schema fully documents the only parameter 'num' with type, range, and description, achieving 100% schema coverage. The description repeats the range (1-22) and provides an example, but adds no new semantic information beyond what the schema already offers, so the baseline score 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 uses a specific verb ('Get') and resource ('one CID-10 chapter and its constituent groups'), clearly distinguishing this from the sibling tool cid10_chapters (which likely lists all chapters) and cid10_lookup. The example with Chapter IX and its groups further clarifies what is returned.

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 clear context with a 'Use this tool to' list covering three practical scenarios (drill into groups, build hierarchical browsers, find containing group). It does not explicitly mention when not to use it or name alternative tools, but the purpose is distinct enough that context is clear.

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