inei_get_districts

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

No annotations provided, so description carries full burden. It discloses that province/district data is unavailable and that the 'ccpp' parameter is ignored. However, it lacks details on authentication, rate limits, or output structure beyond mentioning 'id_geografia'.

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?

Two sentences with no waste, but the first sentence is misleading about the tool's actual purpose (departments vs. districts). Conciseness is good, but clarity suffers.

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?

No output schema, and the description does not specify the structure of the returned data beyond mentioning 'id_geografia'. Given the name mismatch and lack of detail for a simple list endpoint, completeness is insufficient.

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%, and the description adds minimal extra insight: it repeats that 'ccpp' is unused and 'search' is client-side, which is already in the parameter descriptions. Baseline 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 states it returns departments, not districts, contradicting the tool name. Additionally, there is a sibling tool 'inei_get_departments' which likely serves the same purpose, but no differentiation is provided.

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?

No guidance on when to use this tool vs. the sibling 'inei_get_departments'. The description only suggests a follow-up action but fails to clarify selection criteria among similar tools.

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