Transactions Delete Transaction

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

The annotations already indicate destructiveHint=true and readOnlyHint=false. The description adds 'may delete, clear, reset, or otherwise remove data,' which is vague and doesn't clarify whether deletion is permanent or if related data (e.g., attachments) is affected. No mention of required permissions or irreversible consequences.

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 extremely concise (one sentence), but it sacrifices clarity for brevity. It front-loads the purpose but then adds confusing qualifiers. Could be improved by removing the vague 'may' list.

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 the lack of output schema, incomplete parameter documentation, and no behavioral details beyond annotations, the description is insufficient for an agent to fully understand the tool's effect, response, and correct invocation.

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 description coverage is only 50%, with transaction_id and session_path lacking descriptions. The tool description does not explain any parameter semantics. An agent cannot infer from the description alone how to properly fill in required or optional parameters.

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 states 'Delete transaction', which clearly identifies the core action. However, it then adds 'This may delete, clear, reset, or otherwise remove data,' introducing ambiguity about the exact effect. The name and title already indicate deletion, so the extra wording diminishes clarity.

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 guidance is provided on when to use this tool versus alternatives like transactions_update_transaction or transactions_unsplit_transaction. The description does not mention prerequisites, side effects, or context-sensitive usage.

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