kin_transaction_abort

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

Annotations already declare destructiveHint=true and idempotentHint=true, so safety is covered structurally. The description adds real value beyond them: it specifies WHAT is destroyed ('everything staged on it') and a state-dependent refusal after the commit fence, which the annotations do not convey.

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?

Three tight sentences, front-loaded with the core action and effect, followed by usage and a failure boundary. Every clause earns its place with no 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?

No output schema exists, and the description covers action, side effect, and the key failure mode, which is sufficient for a two-parameter transactional tool. The 'fenced' phrasing is slightly terse and could be clearer about the resulting state, keeping it just below a 5.

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%, including the enforce-mode session match caveat, so the description carries no additional parameter burden. It adds nothing beyond the schema, making the baseline 3 appropriate.

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?

States a specific verb and resource ('Abandon an open transaction') plus the scope of effect ('discard everything staged on it'). This clearly distinguishes it from kin_transaction_commit and kin_transaction_stage without the agent needing to open any sibling schema.

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?

Gives two concrete trigger conditions: deciding against a change, and starting clean after a refusal, which implicitly routes the agent away from commit. It also states a boundary condition (refused once commit has fenced it). It does not explicitly name commit as the alternative, so it falls just short of a 5.

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