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

Annotations already declare readOnly/idempotent/non-destructive, and the description adds real behavioral context: prices are all-in SGD with 9% GST and Singapore delivery, and unpriced lines must be surfaced rather than fabricated. It does not discuss rate limits, batch cost, or failure modes for a 50-line call.

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 purpose and return shape before the edge-case rule, and most clauses earn their place. The final sentence is dense and slightly run-on, packing the anti-fabrication rule and the request_quote escalation into one string.

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?

With no output schema, the description takes on the burden and discharges it: it enumerates the per-line returns (match level, all-in SGD price, ready-by date), the aggregate total, and the clarify list. An agent knows what it will get back and when to escalate.

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% and every parameter is already documented there. The description restates the string-vs-object line format ('item, quantity, category, brand, model, specs') without adding syntax or precedence rules beyond the schema, so the 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 and resource ('price a whole shopping list or RFQ in one call') and scopes it to many line items across office/IT supplies and event print, which cleanly separates it from the single-item siblings quote_office_supplies and quote_event_print.

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 explicit routing: use this for bulk lists, and 'convert the list to a firm quote with request_quote (pass list_id)' names the alternative plus the parameter to thread. It also states the negative case ('Never invent prices for unpriced lines') and what to do instead.

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