consultar_aliquotas_importacao

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

Discloses offline behavior (reads from bundled SQLite database, no connection required) and explicitly states the unavailability of the II rate. While it lacks annotations, the description adds substantial behavioral context beyond the schema.

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 well-structured with clear sections for purpose, usage, important notes, and parameter details. Each sentence serves a purpose, and there is no redundant information.

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 simple parameter set and the presence of an output schema, the description adequately covers the tool's role and constraints (offline, missing II). It could briefly mention output structure, but the overall context is sufficient.

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% and already describes the NCM parameter format. The description merely repeats the format with examples, adding no significant new semantic meaning beyond what the schema provides.

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 clearly states it consults reference rates for import tax calculation by NCM, specifically IPI and defaults for PIS/COFINS. It distinguishes itself from the sibling tool 'calcular_tributos_importacao' by identifying its role as a preliminary step.

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 to use ('antes de calcular tributos de importação') and provides a critical warning that the II tax rate is not available offline and must be sourced externally. This guides the agent on both usage and limitations.

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