rtc_base_calculo_mercadorias

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

With no annotations, the description must carry the safety and behavior burden. 'Conferir a montagem da base' conveys a non-mutating, verification-like behavior and 'antes do cálculo' clarifies it does not produce the final tax amount. However, it does not disclose response content, side effects, auth, or error behavior, so transparency is only partial.

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?

Two sentences, no filler, and the core identifier (base de cálculo CBS/IBS mercadorias) is front-loaded before the endpoint and use case. Every sentence earns its place.

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 no annotations, no output schema, and a required nested 'operacao' object with no parameter documentation, the description is not complete enough for correct invocation. It provides selection context but not the structural contract needed to call 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 gives 0% description coverage and the only parameter, 'operacao', is an open object (additionalProperties: true). The description's 'operação com mercadorias' hints at the parameter's domain but does not say what fields the operation object must contain, so an agent has too little information to build a correct request.

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 names a specific resource — the CBS/IBS tax base for goods operations — and gives the intended use ('conferir a montagem da base antes do cálculo do tributo'). It is not a tautology and leaves little doubt about the domain, though it does not explicitly contrast with rtc_nfse_base_calculo or rtc_calcular_tributos.

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 explicitly positions the tool as a pre-calculation check ('antes do cálculo do tributo'), which tells an agent when it is relevant. It does not give exclusions or name an alternative, so it stops short of a 5.

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