cid10_chapter

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

Annotations indicate readOnlyHint=true, destructiveHint=false, idempotentHint=true, openWorldHint=true. The description says 'Get one CID-10 chapter' which is consistent and adds context about returning groups with examples. No contradiction, but the description does not significantly expand on behavioral traits beyond 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 (6 lines), front-loaded with the main action, then bullet points for uses, and a clear parameter instruction. Every sentence adds value, with no waste.

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?

Given the tool's simplicity (single parameter, output schema present, rich annotations), the description fully covers what the tool does, how to use it, and what to expect. It is complete for an agent to select and invoke 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 has parameter 'num' with description 'Chapter number (1-22).' The description repeats this instruction. With 100% schema coverage, the description adds no new meaning beyond the schema.

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 states it retrieves a CID-10 chapter and its constituent groups, providing an example and listing specific uses (drill into groups, hierarchical browsers, find code range). This distinguishes it from siblings like cid10_chapters (which likely lists all chapters) and cid10_lookup (code lookup).

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 explicitly lists three use cases (drill from chapter, build hierarchical browsers, find code range) and instructs to provide a chapter number 1-22. It does not mention when not to use or alternatives, but the use cases are clear and cover the primary scenarios.

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