ibge_populacao

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

Discloses output content (current estimate, birth/death rates, daily increment) and source. No annotations, so description carries full burden; it provides sufficient behavioral details for a read-only projection tool.

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?

Well-structured with bullet points and a helpful note. Concise but complete for the complexity of the tool.

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 simple schema (1 enum parameter), no output schema, and no annotations, the description adequately covers purpose, features, source, and alternative use cases. No gaps.

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?

Input schema covers the single parameter with enum and default (100% coverage). Description adds context that projection is real-time and Brazil-only, but doesn't add semantics beyond 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?

Clear verb (Returns) and resource (Brazilian population projection), with a specific feature list. Distinguishes from sibling ibge_sidra by noting it handles historical/municipality data.

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 states when not to use (historical data or by municipality) and directs to alternative tool (ibge_sidra) with specific table numbers.

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