deleteTransaction

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It only states 'delete transaction' and omits critical details such as irreversibility, effects on recurring occurrences, or any side effects. This is a significant transparency gap for a destructive operation.

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 only three words, which is under-specified rather than concise. While it contains no fluff, it does not convey enough information to be useful; it is essentially a translation of the tool name with no added structure or elaboration.

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?

The description is grossly incomplete for a tool with three parameters and a recurring-transaction feature. It fails to mention how the delete behaves for recurring transactions (whether it deletes only one occurrence, all, or future ones), which is a central aspect of the tool's functionality.

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 provides descriptions for update_all and update_future, but the required 'id' parameter lacks a description. The tool description does not clarify that 'id' identifies the transaction or explain how the boolean flags modify deletion behavior, failing to compensate for the 33% schema coverage 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 'Excluir movimentação' directly translates to 'Delete transaction,' which essentially restates the tool name 'deleteTransaction.' It does not elaborate on the tool's scope (e.g., that it handles recurring transactions) and does not differentiate it from sibling tools like deleteTransfer or deleteAccount.

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?

No usage guidance is provided. The description does not indicate when to choose deleteTransaction over alternatives, nor does it mention the optional recurring-related parameters (update_all, update_future) that are central to using the tool correctly.

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