delete_transaction

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

With no annotations, the description carries the full burden of behavioral disclosure. 'Delete a transaction by ID' only states the core operation without indicating whether deletion is permanent, what happens to associated tags or data, or whether special permissions are needed. It offers no insight into the side effects or reversibility.

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 short sentence with no redundancy or filler. It is efficiently worded and front-loads the essential information about the action and parameter.

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?

Although the tool is simple with only one parameter, the description lacks important context such as the permanence of deletion, any side effects, or the expected return value. This makes it incomplete for an agent to fully anticipate the consequences of invoking it.

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's phrase 'by ID' aligns with the transaction_id parameter but adds no additional meaning beyond the parameter name. Since schema coverage is 0%, the description should compensate by explaining the ID's format, source, or usage, but it does not.

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), the target resource (transaction), and the specific scope (by ID). This distinguishes it from other sibling tools such as update_transaction and create_transaction, which have different operations.

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 given about when to use this tool versus alternatives like update_transaction or mark_transaction_reviewed. There are no prerequisites, exclusions, or recommended contexts mentioned.

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