Transactions Unsplit Transaction

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

Annotations already indicate a non-read-only, non-idempotent write operation, and the description's 'This may create or update Monarch data' adds little beyond that. It does not disclose what happens to split data, whether the operation is reversible, or what side effects may occur.

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 text is short and front-loaded with the action, but the second sentence is generic and adds limited value. It is not verbose, but the brevity borders on under-specification rather than effective conciseness.

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?

For a mutating operation with no output schema, the description fails to explain what 'unsplit' actually does, what changes occur, and what the caller should expect. An agent would not have enough context to invoke this tool correctly or safely.

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 schema leaves transaction_id undocumented, and the description provides no additional meaning for this required parameter. Fields and output_mode have schema descriptions, but the critical required parameter lacks semantic guidance and the description does not compensate.

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 'Unsplit transaction' is essentially a restatement of the tool's name and title, and does not explain what unsplitting entails, such as removing splits from a transaction or consolidating them. It does not differentiate this tool from related transaction tools like transactions_update_transaction_splits.

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 provides no guidance on when to use this tool versus alternatives such as transactions_get_transaction_splits or transactions_update_transaction_splits. No conditions, prerequisites, or exclusions are mentioned.

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