cid10_lookup

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

Annotations already declare readOnly, non-destructive, idempotent, and open-world behavior. The description adds value by specifying input format flexibility (accepts dotted and undotted forms) and that returns canonical display, 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?

Three sentences, each earning its keep: purpose, use cases, and input detail. No waste, front-loaded with core action. Ideal conciseness.

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?

Tool complexity is low (1 param, simple lookup). Annotations cover safety/idempotence, output schema exists (not shown but acknowledged), and description provides input handling and use cases. No gaps remain.

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 covers 100% of the parameter with a detailed description including pattern and examples. The description adds the note about dotted/undotted acceptance and canonical return, but this is minor. Baseline is 3 due to high schema coverage.

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 states 'Look up a specific CID-10 code and return its Portuguese name' which is a clear verb+resource statement. It distinguishes from sibling tools like cid10_search (search by term) and cid10_chapter (list codes), as well as other terminology lookups (ATC, ICD11, etc.).

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 lists three specific use cases (resolve code to description, confirm existence, retrieve restriction flags), providing clear context for when to use the tool. However, it does not explicitly exclude scenarios or mention alternative tools for related tasks.

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