| Name | Required | Description | Default |
|---|---|---|---|
| code | No | ICD code (e.g., A00, J18.9, BA00) | |
| path | No | API path for raw requests | |
| query | No | Search terms (ICD-11 only) | |
| action | Yes | ||
| chapter | No | Chapter code to filter by | |
| version | No | ICD version: 10 or 11 (default: 11) | |
| max_results | No | Maximum results (default 10) |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Tool has no description.
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?
Tool has no description.
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 has no description.
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?
Tool has no description.
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?
Tool has no description.
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?
Tool has no description.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Add one secure layer between your agents and this server.
With only one tool, there is no possibility of confusion or overlap between tools, as there are no other tools to compare it to. The tool's purpose, while undefined, is inherently distinct by default.
A single tool name 'icd' has no other names to be inconsistent with, so naming consistency is perfect by default. There is no pattern to evaluate, but no deviation exists.
One tool is too few for a server named 'icd-mcp', which suggests a domain like medical coding or classification where multiple operations (e.g., search, lookup, validate) would be expected. This minimal count severely limits functionality.
The tool set is severely incomplete for the inferred domain of ICD (medical coding), lacking basic operations like search, get details, or validate codes. With no description, it's impossible to assess coverage, but a single tool cannot provide comprehensive functionality.