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

Annotations cover the safety profile (readOnlyHint=false, idempotentHint=false, non-destructive) but the description adds real value beyond them: the request is emailed to a third party, the business replies directly to the customer, no payment or wallet is involved, and consent gates the disclosure of personal data. It also discloses the return shape (reference + status URL), which matters since no output schema exists.

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 short sentences, front-loaded with the purpose and the eligibility condition, followed by the mechanics (email, reply), the cost/consent constraints, and the return value. Every sentence carries information; no filler.

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 12-parameter, 6-required external-communication tool with no output schema, the description covers the critical unknowns: eligibility, third-party data flow, consent requirement, no payment, and the return value. Minor gaps remain, such as idempotency/retry behavior and what happens on a rejected request.

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 all 12 parameters, including consent, email/phone, and item semantics, are already documented in the schema. The description restates the consent rule and the price_on_request constraint on item but adds no syntax or format guidance beyond that, so baseline 3 applies.

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+resource ('Ask a verified business for a quote') and narrows it to items flagged price_on_request: true, with concrete examples (roofer, lawyer, garage). This distinguishes it from siblings like place_order (which handles priced items) and list_business_offerings (the catalogue it reads from).

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?

Gives a clear precondition for use — the item must be price_on_request in list_business_offerings — and notes nothing is paid or owed, implicitly steering priced purchases to place_order. However, it never names the alternative tool explicitly nor states an explicit when-not-to-use case.

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