Delete Transactions

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

The description adds significant behavioral context beyond annotations: it clarifies that deletions are undoable (by re-creating) and that each deletion costs one API call against the rate limit. This complements the destructiveHint and idempotentHint annotations.

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 exceptionally concise: three short sentences with no fluff. It front-loads the core purpose and immediately adds useful context.

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 deletion tool, the description covers undoability and rate limits, which addresses key usage concerns. However, it does not discuss error handling or what happens on failure, but given the simple nature and rich annotations, it is largely complete.

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 description does not explain any parameter details. With only 50% schema description coverage (budget_id described, transaction_ids not), the description should compensate but fails to do so, leaving transaction_ids semantics unclear.

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 action ('Delete') and the resource ('one or more transactions'), with additional context about undoability. It effectively distinguishes itself from sibling tools like update_transactions and create_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 provides explicit guidance on when to use (to delete transactions) and notes that deletions are undoable, implying an alternative (re-creating). It also mentions rate limits. However, it does not explicitly contrast with other deletion or undo tools.

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