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

Annotations already declare readOnlyHint=false and openWorldHint=true; the description adds real value by disclosing the outcome (a tracking ID is returned) and the downstream effect (an engineer replies to the work email within 24 hours), which tells the agent this is an externally visible commitment. It stops short of warning that the call is non-idempotent, so repeat submissions may create duplicate RFQs — the one behavioral trait an agent most needs warned about here.

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 sentences, each earning its place: purpose, precondition, then return/outcome. The gating condition is front-loaded before the consequence, which is the right ordering for an agent deciding whether to call.

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 13-parameter submission tool it covers the essentials — who it acts for, the required identity fields, and what comes back without an output schema. The remaining gap is the non-idempotent behavior: an agent is not told whether retrying a failed submission is safe.

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 restates the four required identity fields but adds nothing about the domain parameters (products, quantity, networkDistance, technicalRequirements) beyond what the schema already documents, and does not explain how the optional fields affect quote quality.

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?

Specific verb+resource: submits an RFQ to OptiLibra on behalf of a buyer. It is unambiguously distinct from the sibling tools get_product and search_products, which are read/lookup operations, so an agent can route correctly without opening any 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?

It states an explicit gating condition — 'Only call this when the buyer has asked for a quote and provided their real name, work email, company and country' — which functions as both when-to-use and when-not-to-use. The prerequisites are concrete enough to be checked before invocation.

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