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

Beyond the annotations, the description discloses important side effects: each counter overwrites the standing offer, keeps the thread in 'quoted', restarts the buyer's acceptance SLA, and does not trigger a charge. It also notes that caps and confirmation are re-checked at accept time, which prevents an agent from assuming payment or finalization happens here.

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 front-loaded with the core action, then adds role eligibility, behavioral side effects, limits, and no-charge clarification in dense but focused sentences. Every clause contributes operational information needed to invoke the tool correctly, with no filler or repetition.

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 negotiation tool with no output schema, the description covers actor eligibility, haggling requirements, SLA restart, the 6-counter bound, and absence of payment. This is more than enough for an agent to decide when and how to call it correctly, and the constraints align with the schema and annotations.

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% and each parameter already has a clear schema description: quote thread UUID, price in pence, ETA in minutes, and optional terms. The description only paraphrases these ('price in pence, ETA in minutes, optional terms') without adding meaningful new parameter-level guidance, so the baseline score of 3 is 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?

The opening line, 'Post a counter-offer on a quote thread,' names the action and resource precisely. The description also clarifies the buyer/seller roles and positions this as a counter/revise operation distinct from initial quote submission or acceptance, making it easy to separate from sibling tools like services_submit_quote and services_accept_quote.

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 gives explicit conditions for when the tool is valid: the buyer may counter only when haggling is enabled, while the seller may counter or revise pre-accept. It also states a hard boundary — after 6 counters only accept or reject are allowed — which directly steers an agent toward the appropriate alternative.

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