Download IBGE Microdata File

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

Annotations already declare readOnlyHint=true, openWorldHint=true, idempotentHint=true, destructiveHint=false. The description adds specific caching behavior: mirrors URL under cacheRoot, checks HEAD content-length, skips re-download if size matches. No contradictions.

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 paragraphs, first sentence front-loads the purpose, second adds caching details and usage guidance. No wasted words, efficient structure.

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?

Covers caching mechanism, prerequisite usage of sibling tool, and local-first approach. However, lacks description of return value (likely local path), which is a minor gap given 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 descriptions for both url and cacheRoot. The description adds 'mirrors the ftp.ibge.gov.br URL under cacheRoot' which is already implied by schema descriptions. It does not provide new parameter-level semantics beyond caching behavior, so 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 starts with 'Download or reuse a selected official IBGE microdata file in a local cache path,' which clearly states the verb and resource. It distinguishes itself from siblings like ibge_microdata_file_info (info before download) and extraction tools.

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 advises to use ibge_microdata_file_info first for large files so the user understands size before downloading. This provides clear when-to-use guidance and differentiates from sibling tools.

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