simular_transicao_reforma_tributaria

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

Discloses that the tool simulates, compares old vs new tax burdens, applies transition blending, and returns annual projections with premises and disclaimers. Without annotations, this is a reasonably transparent description, though it could be more explicit about data sources or underlying assumptions.

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?

Compact and well organized: the opening sentence states the main purpose, followed by input guidance and an output note. The only minor redundancy is restating sector/regime values that are already present in the schema, but it does not hurt readability.

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 that an output schema is present, the description covers the essential context: what is simulated, what inputs matter, and what the return contains (annual projection, premises, disclaimers). It could be slightly stronger by explicitly mentioning limitations or edge cases, but it is adequate for the tool's complexity.

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 already documents all six parameters. The description adds meaningful context by reinforcing accepted sector/regime values, indicating which aliquotas are optional for better precision, and clarifying that PIS/COFINS defaults depend on the selected regime.

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?

States a specific verb ('Simula'), a clear object ('impacto da Reforma Tributaria (LC 214/2025)'), a definite time horizon (2026-2033), and the core comparison between old and new regimes. This distinguishes the tool from generic tax calculators and gives a precise sense of its purpose.

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?

Provides useful context on what the simulation does and notes that optional aliquotas can improve precision. However, it does not explicitly state when to use this tool instead of sibling tools such as compare_tax_regimes, nor does it give exclusion criteria or recommended usage scenarios.

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