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

Annotations only cover readOnly=false, idempotent=false, destructive=false and openWorld=true. The description adds substantial context beyond that: the request is emailed, the business replies directly to the customer, nothing is paid or owed, no wallet is needed, and consent must be obtained from the customer first — all critical behavioral facts not derivable from the annotations.

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?

Four dense sentences: eligibility, mechanism, cost/consent constraint, and return value — front-loaded with the eligibility condition and no filler. Each sentence carries a distinct decision-relevant fact.

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?

Despite 12 parameters with no output schema, the description closes the important gaps: it explains the consent gate, that no payment occurs, and that the call returns a reference and status URL. For a write-ish, open-world tool, nothing an agent needs to call it 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 description coverage is 100%, so the baseline is 3. The description adds value by tying consent to its legal/UX meaning ('ask the customer first, send consent: true only if they agreed their name, contact and request go to the business') and by framing email/phone as the reply channel, going slightly beyond the field descriptions.

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 gives a specific verb and resource — request a quote from a verified business — and narrows scope to items marked price_on_request, distinguishing it from place_order (which handles priced items). An agent can tell immediately what the tool produces: an emailed request and a quoted price back to the customer.

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 states the use condition clearly (item must be price_on_request: true in list_business_offerings) and names that sibling as the source of the item. It does not explicitly name place_order as the alternative for priced items, so the exclusion from buying flows is left to inference.

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