deleteTransaction

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The verb "Deletes" signals destructiveness, but nothing is said about whether the deletion is permanent, what side effects occur on linked data, or error conditions. For a destructive tool, this is a significant transparency 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 single sentence is grammatically complete, but at four words it is under-specified rather than appropriately concise. For a destructive operation with no annotations, the brevity is a deficiency — there is no front-loaded scope, caveat, or guidance, just a restatement of the name.

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?

This is a destructive tool with no annotations and no usage guidance, yet the description contains only a restatement of intent. It doesn't address permanence, when to use it, prerequisites, or any behavioral caveats an agent would need to invoke it correctly. The effort level is well below what the tool's complexity demands.

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 100%, so the baseline is 3. The schema fully documents plan_id (including the "last-used"/"default" special values) and transaction_id. The description adds nothing about parameters, but the schema already carries that weight.

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?

"Deletes a transaction" states a specific verb and resource, and the resource type distinguishes it from the sibling deleteScheduledTransaction. However, it's essentially a restatement of the tool name with no added scope detail, so it's clear but minimal.

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 gives no guidance on when to use this tool versus alternatives like updateTransaction (which can change transaction state) or deleteScheduledTransaction. There's no context, no exclusions, and no when-not-to-use guidance, so an agent must infer usage entirely from the name.

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