Cleanup Local IBGE Cache

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

Adds context beyond annotations: scope limited to cacheRoot/ftp.ibge.gov.br, need for filters, dryRun default, and requirement for user consent before deletion. 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?

Three sentences, each essential: core purpose, scope/filters, and safe workflow. No wasted words.

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?

Fully covers all critical aspects: what it does, cache scope, required filters, default behavior, and safe usage. No gaps for effective agent selection and invocation.

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%, but description adds value by highlighting the filter requirement and dryRun default, aiding correct usage beyond schema descriptions.

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?

Clearly states 'Preview or delete selected files from the local IBGE microdata cache,' specifying verb and resource. Distinguishes from sibling tools like download and list.

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 requires at least one filter (olderThanDays, minBytes, or urlPrefix) and outlines the safe workflow: preview with dryRun=true, then set dryRun=false only after user agreement.

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