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

With no annotations, the description carries the full burden. It usefully discloses that this stops an open hand-off and that either the owner cancels or the recipient declines, but it omits permission requirements, irreversibility, behavior for closed/completed transfers, and error conditions.

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?

A single front-loaded sentence with no filler. It communicates the action and the two initiating roles efficiently.

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?

An output schema exists, so return values need not be explained. Still, as an unannotated mutation tool, the description leaves key preconditions and parameter semantics implicit, making it only minimally adequate for reliable invocation.

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 0%, and the description never mentions transfer_id or its UUID format. The single parameter can be inferred from context, but the description does not compensate for the missing schema documentation.

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 uses a specific verb ('Stop') and resource ('open hand-off'), and distinguishes cancellation by owner from decline by the invited person. It is clear enough to separate this from sibling listing tools like shops_transfers, though 'hand-off' is slightly less direct than 'transfer'.

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 phrase 'open hand-off' implies this applies only to transfers still pending, and the two actor scenarios are named. However, it doesn't explicitly state when not to use it, what alternative to use, or how to obtain a transfer_id.

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