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

Beyond the annotations (openWorldHint=true, idempotentHint=false), the description discloses that this is an outbound message to an external party with a one-business-day email reply, and imposes a human-confirmation gate — real behavioral context. It stops short of describing failure behavior or what happens on resend/duplicate submission for a non-idempotent send.

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 tight sentences, front-loaded with purpose, then the gate condition, then detail. The trailing market sentence is dense and slightly crammed with quoted enum values, but no sentence is 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 10-parameter outbound-send tool with no output schema, the definition covers what it does, the mandatory human approval, the recipient and expected reply, and how to pick the market. That is enough for an agent to call it correctly; the only mild gap is error/resend behavior.

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?

With 60% schema coverage across 10 parameters, the description compensates for the most ambiguous ones: it explains the two market enum values, the meaning of buyer_confirmed, and where product_id should come from. It says nothing about phone, message, delivery_date, or delivery_location, though those carry their own schema 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 first sentence gives a specific verb and resource plus the recipient: 'Send a quotation request to Unan Trading on the buyer's behalf.' It also states the outcome channel and latency, which clearly separates it from the read-only siblings (search_products, list_brazil_export_offers, get_company_info).

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?

Explicit precondition is stated: use only after the buyer has seen the exact details and asked for them, with buyer_confirmed=true as the proof. It also adds a negative rule ('Do not invent contact details') and routes the agent to search_products for product ids, and explains which market value applies to which order type.

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