Get ICD-10 Codes

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

Annotations already indicate readOnlyHint=true, making it a safe read operation. The description adds behavioral details: it returns approved/supportive codes, avoidance codes, and tips. The 'PREMIUM tier' note hints at access restrictions but is not fully explained. No contradiction with 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 a single, dense sentence that conveys the input, output components, and tier. No unnecessary words, perfectly concise for its purpose.

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 single parameter and no output schema, the description adequately outlines the output (codes, avoidance codes, tips). It could be more precise about the output format (e.g., list vs. structured), but it covers the essential information needed for an agent.

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 coverage is 100% with the parameter 'procedure' described as 'Procedure name, id, or CPT code.' The description does not add any additional parameter semantics beyond the schema, 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 clearly states the tool returns ICD-10 diagnosis codes, codes to avoid, and coding tips for a given procedure. It distinguishes itself from siblings like get_cpt_codes (CPT codes) and get_contraindications.

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 implies usage for obtaining ICD-10 codes, but lacks explicit guidance on when to use this vs. alternatives (e.g., when not to use, or when to use siblings). The context from sibling names provides some differentiation, but the description itself does not.

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