Excluir cálculo do PJe-Calc

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. The description adds real substance beyond that: the operation is IRREVERSÍVEL and requires the exact string "SIM, EXCLUIR" as confirmation.

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?

Three short sentences, front-loaded with the action, then the irreversibility warning, then the backup pointer. Nothing is redundant.

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 two-parameter destructive delete with no output schema, the description covers the only things an agent needs: the exact confirmation value, the irreversibility, and the safe alternative. Nothing material is missing.

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% and both parameters (id_calculo, confirmacao) are documented in the schema, including the exact confirmation string. The description's mention of confirmacao repeats rather than extends the schema, so the baseline 3 applies.

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?

Specific verb ('Exclui') plus resource ('um cálculo do PJe-Calc') and even the UI path (Operações > Excluir). It is clearly distinguishable from siblings like calculo_criar, calculo_atualizar and calculo_exportar_pjc.

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?

Gives explicit prep guidance: call calculo_exportar_pjc first if you want to keep the calculation, and states the mandatory confirmation token. It does not spell out conditions under which deletion should be avoided, but the routing advice is clear.

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