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

Goes well beyond the annotations by disclosing the real-world side effect ('Real e-mails are sent'), the anonymity behavior (the Exchange contacts suppliers for the buyer), and hard prerequisites (verified e-mail, Business+ plan). The instruction to confirm selection with the user first is exactly the kind of operational guidance annotations cannot convey.

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?

Front-loads the core action and resource in the first sentence, and each clause carries information (prerequisites, defaults, anonymity, the e-mail warning). The middle em-dash clause is dense and slightly run-on, but there is 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, zero-required mutation tool with side effects and no output schema, the description covers the critical prerequisites, the two targeting paths, and the confirmation warning. It is thin on the quantity/unit/currency/target_price and broadcast parameters, which an agent filling the form would still have to infer from the schema alone.

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 58% across 12 parameters; the description adds real meaning for listing_ids and company_slugs (their source and the anonymous-contact behavior) and implies material_id/project_id usage, but quantity, unit, currency, target_price, needed_by, notes, region and especially broadcast get no mention. Note also that the description sources listing_ids from find_suppliers while the schema says search_exchange_listings.

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 ('Request quotes on the OPN Trade Exchange') plus scope (a Design Studio project or a PackIndex material code, up to 3 suppliers). This clearly separates it from siblings like get_my_rfqs (read) and find_suppliers (discovery), so an agent can pick it without opening the schema.

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?

Explains the two targeting modes (listing_ids, or best-matching listings by default; company_slugs to ask specific converters) and names prerequisites (verified e-mail, Exchange plan with RFQs / Business+). It points to find_suppliers as the source of IDs, but does not say when to choose material_id/project_id over listing_ids/company_slugs, so it stops short of full when/when-not coverage.

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