ynab_delete_transaction

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

Description mentions irreversibility, aligning with destructiveHint annotation. Adds dry_run parameter and return info. Annotations already provide destructiveHint=true, but description adds preview behavior and error scenarios, adding value beyond 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 concise, front-loaded with purpose, and structured into clear sections (Args, Returns, Errors). Every sentence provides value without redundancy.

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 simple tool with 3 parameters and output schema present, the description covers all necessary context: parameter details, return values, and error handling. An agent can confidently invoke the tool.

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?

Despite 0% schema coverage, the description fully describes each parameter: budget_id (optional, default), transaction_id (required), dry_run (optional, default false). This adds significant meaning beyond the bare schema.

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 'Delete a transaction from YNAB' with the verb 'delete' and resource 'transaction'. It uniquely distinguishes from siblings as there is no other delete transaction tool.

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 implies usage (when you want to delete a transaction) but does not explicitly state when to use this tool vs alternatives like update for cancellation. No exclusions or context provided.

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