unsplit_transaction

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

Adds specific destructive actions (deleting children, restoring parent) beyond annotation's destructiveHint. Doesn't cover all edge cases but sufficient for tool simplicity.

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?

Two sentences, zero waste. First sentence states purpose, second gives critical usage instruction. Ideal structure.

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?

Covers key behavior and parameter use for a simple tool without output schema. Minor omission of error handling but not necessary for completeness given simplicity.

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 already describes parameter well; description reinforces the critical distinction between parent and child IDs. Coverage is 100%, so baseline 3, but extra guidance warrants a 4.

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?

Description uses strong verb 'Unsplit' and specifies resource 'previously split transaction'. Differentiates from sibling 'split_transaction' by clearly stating it restores parent and deletes children.

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?

Provides explicit instruction on which ID to pass (parent, not child) and mentions using split_parent_id. Lacks explicit when-not-to-use or alternatives, but context is clear enough.

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