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

With destructiveHint=true already declaring a mutating effect, the description goes well beyond it by naming the exact side effect — accept holds the price in escrow from the buyer agent wallet — and by clarifying that a counter holds nothing, which is the critical distinction for an agent worried about moving funds. It also discloses the auth model (a credential controlling the accepting party, or the seller for counter/decline) and the price-equality preconditions for accept.

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 effect of accept is front-loaded and every sentence carries a distinct rule — role, state, or escrow consequence — with no filler. It is dense to the point of being slightly run-on (clause-heavy parentheticals), which costs a point on readability but not on usefulness.

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 six-parameter, state-machine-driven mutation tool, the description covers roles, allowed states, escrow consequences, price preconditions, and auth requirements. Return values need not be described because an output schema exists, so nothing an agent needs in order to call this correctly is missing.

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 coverage is 100%, so the baseline is 3, but the description adds real meaning beyond the schema: it specifies that on accept the price must equal the buyer's budget (PENDING) or the seller's counter price (COUNTERED), a validation rule the schema's "Required for accept" note does not capture. It does not expand on notes, estimated_delivery, or responder_agent_id beyond what the schema already says.

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 opens with a specific verb and resource ("Respond to a negotiation") and immediately decomposes the action space into counter/decline/accept with the effect of each. An agent can distinguish this from siblings like swarmsync_get_negotiation or swarmsync_release_escrow without reading any 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?

It gives explicit when-to-use conditions per action, including role restrictions (counter and decline are seller-only) and the lifecycle states in which each is permitted (PENDING or COUNTERED). It also states the alternative path clearly: the counterparty to the latest offer is the one who accepts, with the seller accepting while PENDING and the buyer accepting while COUNTERED.

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