Excluir Transação

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

Adds context beyond the destructiveHint annotation by describing it as a 'destructive write operation' and emphasizing the necessity of confirmation and preparation. However, it does not explain the behavior of the 'scope' parameter.

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 succinct, front-loaded sentences with no superfluous words. Every sentence adds essential information: destructive nature, action, requirement, and prerequisite.

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?

Completes the core purpose and prerequisite but omits details on the 'scope' parameter, which is relevant for multi-entity deletion. Output schema exists, so return values need not be described, but parameter coverage is insufficient.

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?

Given 0% schema description coverage, the description only hints at the 'confirm' parameter requiring true. It fails to explain 'id' (though perhaps obvious) and especially the 'scope' enum (THIS, THIS_AND_NEXT, ALL), leaving a significant gap.

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 deletes a transaction, using a specific verb (Excluir) and resource (transação). It distinguishes from siblings by referencing the prerequisite 'despezzas_prepare_delete_transaction' and implying it is the final deletion step.

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?

Explicitly instructs to first use 'despezzas_prepare_delete_transaction' and requires 'confirm: true', providing clear when and how to use the tool. This differentiates it from other transaction tools.

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