compare_tax_regimes

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

The description discloses what the tool returns (estimated effective rate, annual tax, best option) and highlights the special impact of payroll on the R factor in Simples. Since no annotations are provided, this is a good level of behavioral transparency, though it does not mention side effects or read-only nature.

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 brief and to the point, using a few short sentences. No redundant information or fluff; every sentence adds value.

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?

For a simple calculation tool, the description provides sufficient input context and output expectations. It doesn't detail the output schema structure, but the mention of three specific result types is adequate for an agent to select and use the tool correctly. Error handling and edge cases are not mentioned, which is acceptable given the tool's simplicity.

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 description adds meaningful context beyond the bare schema: it specifies allowed sectors (comércio, serviços, indústria) and explains that the optional payroll affects the R factor in Simples. However, it does not explicitly define 'faturamento_anual' beyond the obvious name, so a slight gap remains.

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 the tool compares Brazilian tax regimes (MEI, Simples Nacional, Lucro Presumido, Lucro Real) for a given revenue and sector, and returns estimates. The verb 'Compara' and explicit list of regimes make the purpose specific and distinguishable from sibling tools.

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?

It provides some context ('Util para planejamento tributário rápido') and mentions the optional payroll impact on the R factor, but does not explicitly state when to use this tool versus alternatives or when not to use it. Guidance is implied rather than explicit.

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