inei_get_indicator_data

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

With no annotations provided, the description carries full burden. It reveals important behavioral info: due to API changes, it returns all available census data rather than a filtered indicator, and instructs to scan sections. This adds significant value beyond schema.

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 front-loaded with purpose and prerequisites, then a note, then common IDs. It is reasonably concise, though the bold structure adds visual clarity. Could be slightly more compact without losing information.

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 no output schema, the description explains returns (census profile with categories) and hints at structure (seccion1/seccion2), but lacks detailed response format or error handling. Adequate but not fully comprehensive for a tool with no output schema.

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 clear descriptions. The description adds extra context (common indicator IDs and emphasis on requiring both parameters) but contradicts schema by stating id_geografia is required when schema marks it optional. This reduces clarity.

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?

Description clearly states 'Get census data for a geography, referencing a specific indicator ID.' It distinguishes the tool from siblings by emphasizing both indicator and geography IDs are needed, and notes an API change that affects output, adding specificity.

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?

Explicitly lists prerequisites (id_indicador from inei_search_indicators, id_geografia from inei_get_departments), providing context on when to use. However, it does not mention alternatives or when not to use this tool, which would be helpful given sibling tools like inei_get_census_dashboard.

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