População de Município (Censo 2022)

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, reducing the burden on the description. The description adds the specific census year and reference IDs, but no additional behavioral details such as return format or error handling. 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 compact and front-loaded with the main purpose. The block of capital IDs is reference material that takes up significant space but is useful for quick validation. No redundant or vague sentences.

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?

For a simple single-parameter tool with rich annotations and a complete schema, the description adequately explains what the tool does, the census source, and how to obtain the required ID. It does not describe the return value, but with no output schema and low complexity, this is a minor gap.

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 provides 100% coverage with a clear description of municipio_id. The description reinforces the 7-digit format and, more valuably, lists concrete example IDs for capitals, which helps the agent construct valid inputs without external lookup.

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 starts with the specific verb 'Consulta' and resource 'população de um município', clearly scoped to the Censo Demográfico 2022. This distinguishes it from sibling tools like ibge_populacao_estados (state-level) and ibge_populacao_censo2022 (general census query).

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 gives clear context for when to use the tool (municipality population from 2022 Census) and provides a pointer to ibge_listar_municipios for obtaining the ID. It does not explicitly exclude alternatives like ibge_estimativas_populacionais, but the title and description make the intended use unambiguous.

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