consultar_csv_zip_pr

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

Annotations already declare readOnly, openWorld, idempotent, and non-destructive. The description adds substantial behavioral detail: it reads by HTTP ranges, does not extract files to disk, filters are accent-insensitive substrings combined with AND, and cursor tracks examined records. It also enumerates valid encodings. This goes well beyond the annotations without contradicting them.

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 compact and front-loaded: the core operation appears first, followed by actionable usage details and a routing note. Every sentence contributes a distinct fact, with no repetition or filler.

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?

An output schema exists, so return-value documentation is unnecessary. The description covers preconditions, pagination semantics, filtering behavior, encoding choices, and the correct sibling for nested PIT data, making it sufficient for an agent to invoke the tool correctly.

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 description coverage is 0%, so the description must compensate. It explains cursor, filtros, and encoding meaningfully. url, arquivo, and limite are somewhat inferable from the tool name and defaults, but limite is not explicitly described, so it falls just short of complete parameter coverage.

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 opens with a specific verb and resource: consult a CSV/TXT inside a ZIP via HTTP ranges. It also distinguishes itself from consultar_dados_pit_pr by noting that the sibling handles nested ZIPs/XMLs, so an agent can tell exactly what this tool is for.

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 gives explicit preparation steps: list the members first and query without filters to discover fields. It also provides a clear when-not-to-use condition by directing the agent to consultar_dados_pit_pr for the consolidated PIT case, leaving no ambiguity about routing.

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