calcular_tributos_importacao

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

With no annotations, the description fully discloses behavioral traits: it explains the cascade order, the need for user-supplied II rate, and lists out-of-scope items. This compensates for the lack of annotations, though the output structure is not described (but output schema exists, so per rules not required).

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 relatively long but well-structured: purpose, usage, important notes, cascade details, disclaimer, parameter list. It is front-loaded with purpose. Some redundancy could be trimmed, but overall efficient given the complexity.

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 tool's complexity (9 parameters, cascade calculation, no annotations, output schema exists), the description covers all major aspects: purpose, usage, cascade method, required user action, disclaimer, and parameter list. It is complete for an AI agent to understand and invoke 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 coverage is 100%, so baseline 3. The description adds value by explaining the cascade relationship and the need to get aliquota_ii from the TEC website, which is not in the schema. However, it mostly repeats parameter names.

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 explicitly states 'Calcula os tributos de importação em cascata para um produto classificado por NCM', providing a specific verb and resource. It distinguishes from sibling tools like 'consultar_aliquotas_importacao' by focusing on cascading calculation.

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 includes 'Quando usar: ao planejar uma importação e precisar estimar o custo total de tributos', giving clear context. It does not explicitly state when not to use or directly compare with siblings, but the disclaimer about scope provides some exclusion guidance.

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