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

Annotations already declare readOnlyHint=false, idempotentHint=false, openWorldHint=true and destructiveHint=false. The description adds genuinely new context: it is a KEYED tool requiring a valid API key, and the follow-up happens out-of-band, so the agent knows there is no synchronous result to wait on.

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?

Three tight sentences, front-loaded with the core action, then the auth constraint and the post-submission behavior. Little waste, though the value-add content is compressed.

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 mutation tool with no output schema and nested objects, the description covers auth requirements and the asynchronous follow-up, which are the key behavioral gaps. It does not mention limits (e.g. max 50 items), but those live in the schema.

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 67% and each parameter is described in the schema. The description only summarizes 'one or more SKUs with buyer contact info', mapping to items and contact but adding no format or constraint detail beyond the schema.

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: submit a quote request for SKUs with buyer contact info. It is clearly a mutation/request tool, distinguishable from the read-only siblings (get_price_and_lead_time, get_product_details, search_products), though it never names those alternatives.

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?

There is no guidance on when to use this versus the read-oriented siblings, nor on prerequisites beyond the API key. The only implicit cue is that it submits a request rather than fetching pricing.

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