transaction.rollback

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

Annotations declare destructiveHint=true, so the agent knows this is destructive. The description adds only the jargon 'Guarded Harness lifecycle operation', which does not explain what is destroyed or the side effects of rolling back (e.g., reverting all changes since begin, invalidating the transaction ID). It fails to disclose any behavioral detail beyond the annotation.

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, which is concise, but it is under-specification rather than efficient writing. It essentially restates the tool name without adding explanatory value. Every word is wasted because it does not clarify purpose or usage. The brevity is not a virtue here.

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 this is a destructive transaction operation with an output schema, the description should explain the transaction lifecycle (e.g., rollback requires a prior begin, discards pending changes). It does not. The agent is left without knowledge of when to call this, what happens to the transaction, or the meaning of 'Guarded Harness'. This is inadequate for a mutation tool with no other context.

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%: both _requestId and _transactionId have meaningful descriptions. The tool description adds no extra parameter semantics, so the baseline of 3 applies. The description's phrase 'lifecycle operation' hints at the transaction context but provides no additional meaning beyond the 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 identifies the operation as 'transaction.rollback' and a 'Guarded Harness lifecycle operation', which names the verb and resource. However, it does not state what rollback actually does (e.g., discard changes, end the transaction), leaving the agent to infer from the name and sibling tools. It distinguishes from begin/commit by name but not by behavior.

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 like transaction_begin or transaction_commit. It does not mention prerequisites (e.g., an active transaction), nor any conditions that would call for rollback instead of commit. No exclusions, no context.

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