consultar_aliquotas_importacao

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

Since no annotations are provided, the description carries full responsibility for disclosing behavior. It transparently states the offline behavior (reads from a bundled SQLite TIPI database, requires no connection) and explicitly notes a limitation (II rate not available offline), giving a clear picture of what the tool does and does not provide.

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 labeled sections (Purpose, Quando usar, IMPORTANTE, Comportamento offline, Parâmetro) but contains minor redundancy, such as repeating 'antes de usar calcular_tributos_importacao' in both the purpose and usage sections. Overall it is informative without being excessively verbose.

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?

The description provides comprehensive context for a query tool: it specifies the input, the output scope (IPI, PIS/COFINS), the key limitation (II not available), and the offline behavior. Given that an output schema is indicated to exist, the description sufficiently covers what an agent needs to decide when and how to use the tool.

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?

The schema covers the single parameter 'ncm' with a clear description, and the tool description reinforces the expected format ('código NCM com 8 dígitos, com ou sem pontuação') with examples. This leaves no ambiguity about the parameter's meaning or accepted values.

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 that the tool queries reference rates for import tax calculation by NCM, specifically to obtain IPI and PIS/COFINS defaults. It also explicitly names the distinct purpose of feeding into calcular_tributos_importacao, making the tool's role unambiguous.

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 provides explicit 'Quando usar' guidance, stating to use this tool before calculating import taxes and to verify IPI and PIS/COFINS defaults. It also warns that II (Imposto de Importação) is not available offline and directs users to consult an external source, effectively distinguishing this tool from related ones.

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