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

Annotations cover the safety profile (readOnly=false, destructive=false, idempotent=true), so the description's job is to add side-effect context — and it does: it discloses that acceptance creates an order, may return a payment link the buyer must complete, or triggers an email invoice as the fallback. It omits the idempotency guarantee (re-accepting is safe), which would be valuable for a mutating tool, so it's not a 5.

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?

Two tightly written sentences, with the core action and result front-loaded and the payment contingencies following. No filler or restated boilerplate.

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?

With no output schema, the description correctly carries the return-value burden, naming order_id and the conditional payment link, and it explains the offline email fallback. It would be complete at 5 if it also addressed whether calling again on an already-accepted quote is safe, given idempotentHint=true.

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 both parameters are fully documented, including the 'ready' status requirement and the confirm authorization semantics. The description adds no syntax or format detail beyond the schema, which is the expected baseline for fully covered parameters.

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 ('Accepts a ready quote') plus the concrete outcome ('returns an order_id'), which cleanly separates it from the read-only siblings get_quote/get_order. An agent immediately knows this transitions a quote into an order.

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 embeds the applicability precondition ('a "ready" quote'), matching the schema's rfq_id constraint, so the agent knows when this tool applies. It does not name explicit exclusions or alternatives, but none of the siblings (get_order, get_quote, get_supplier_capabilities, submit_rfq) are substitutes for this action, so the gap is minor.

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