Estimativas Populacionais Anuais

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

Annotations already declare readOnly, idempotent, and non-destructive behaviors, so the description has a lower burden. It adds context about TCU usage and annual updates, but doesn't disclose response format, default behavior when optional params are omitted, or error handling. Adequate but not rich.

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 well-structured with a clear first sentence and a bulleted parameter list. It is concise and front-loaded with purpose, though the final example sentence adds a bit of redundancy without much new 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?

The description covers purpose, scope, parameters, and usage guidance, but the schema contradiction regarding localidade creates a critical completeness gap. An agent cannot reliably invoke the tool based on this description, so it falls short of being complete.

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 description adds examples and explanation, but it explicitly states localidade can be an IBGE code while the input schema restricts it to an enum of 'BR' and 'estados'. This direct contradiction misleads the agent and will likely cause invalid calls, making the description worse than merely relying on the schema.

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 queries annual population estimates for inter-census years (2001-2024+), distinguishing it from sibling tools like the 2022 census. The TCU context and annual update cadence reinforce a specific, well-scoped purpose.

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 explicitly says 'Use para dados mais recentes que o Censo 2022 ou para anos intermediários', providing clear context on when to choose this tool. It doesn't name alternative tools or exclusions, but the scope is defined well enough for an agent to make an informed selection.

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