delete_transaction

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

The description essentially restates the tool name and adds no behavioral context. It fails to disclose whether deletion is permanent, requires special permissions, or has side effects on related data, and no annotations are provided to fill this gap.

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 a single, direct sentence with no superfluous words, making it highly concise and easy to parse.

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?

While the tool has a simple parameter set, it lacks annotations and an output schema. The description does not explain the result of deletion, irreversibility, or any related behaviors, leaving an agent without important context for a destructive operation.

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 input schema fully documents the transactionId parameter with a clear description, so the baseline is 3. The tool description adds no additional parameter semantics beyond what the schema already covers.

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 uses the specific verb 'delete' and resource 'transaction', clearly stating it removes a single, identified transaction. This distinguishes it from sibling read/list tools like get_transaction and list_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?

No guidance is provided regarding when to use this tool vs alternatives. It does not mention prerequisites, exclusions, or how it relates to other transaction tools.

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