Remove Transaction

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

The description discloses the conflict-first behavior, the automatic handling of transfer legs, and the recoverability of actions. It mentions the balance effect reversal for permanent deletion. Without annotations, this provides adequate transparency.

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 three sentences long, efficiently covering all essential aspects. No redundant information.

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 output schema, the description explains the conflict return and the effect of each resolution. It could mention the final response after confirmation, but the main interaction is well-covered.

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%, but the description adds context on the two-step flow, resolution meanings, and deprecated fields. This adds value beyond the schema, explaining the interaction pattern.

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 removes a transaction by archiving or deleting, and explains the two-step conflict resolution. It distinguishes well from sibling tools focused on adding or listing transactions.

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?

The description explains the two modes (archive vs delete) and the conflict-first interaction. It provides guidance on handling transfer legs. However, it does not explicitly contrast with other removal tools like remove_account, but this is not needed as the tool is transaction-specific.

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