Convert Fixed-Width IBGE File to Parquet

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

Annotations already declare idempotentHint=true and destructiveHint=false. Description adds that this is an 'optimization path' but does not disclose any additional behavioral traits such as file overwrite behavior or performance characteristics.

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 sentences for the description and two for usage context. Every sentence conveys necessary information without redundancy. Front-loaded with the core action.

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 the 100% schema coverage and no output schema, the description provides sufficient context: specifies the type of files (PNAD, POF), the optimization rationale, and variable selection advice. No gaps identified.

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%, so parameter descriptions already cover semantics. Description reinforces the ability to select variables but adds no additional meaning 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?

Clearly states conversion from fixed-width IBGE microdata TXT to Parquet using an official layout. Differentiates from siblings like 'fixed_width_zip_to_parquet' by specifying local TXT files and mentioning specific surveys (PNAD, POF).

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 the tool is for repeated analysis and recommends selecting only needed variables. Implies use for fixed-width files from IBGE microdata families. Does not explicitly mention when not to use or alternatives, but sibling tool name suggests zip-to-parquet alternative.

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