cid10_hierarchy

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

No annotations are provided, so the description must fully disclose behavioral traits. It states the tool returns all codes under a prefix but does not describe the return format (e.g., list of full codes with descriptions), side effects, or authentication requirements. This leaves the agent with incomplete behavioral understanding.

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 two sentences, front-loaded with the core purpose, and every sentence adds value. No unnecessary words or repetition.

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 has one parameter (100% schema coverage) and no output schema. The description explains what it does and gives an example, but it does not describe the return structure (e.g., list of strings, objects with descriptions). This omission limits completeness for an agent invoking the tool.

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 schema describes the 'prefixo' parameter with examples, achieving 100% coverage. The description adds an example of usage ('prefixo E11 retorna todos os tipos de diabetes mellitus tipo 2'), providing context beyond the schema definition.

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 retrieves all CID-10 codes under a category/prefix, with a specific verb 'Retorna' and resource 'códigos CID-10'. It distinguishes from sibling tools like cid10_search (search) and cid10_lookup (single 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 provides a clear usage context ('Útil para obter todas as subcategorias de uma condição') and an example with prefix 'E11'. However, it does not explicitly state when not to use this tool or mention alternative sibling tools.

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