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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), and the description adds real value on top: the returned payload's field shape and unit convention (pence), the fact that it is re-validated under Nero Work's own rules, and the extras-inclusion behavior. What is missing is what happens when validation fails and whether the result is meant to be copied verbatim into submit_quote.

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?

Two sentences, no filler, and the most useful information (the target exchange's exact argument shape and its validation) is front-loaded. The opening sentence is a dense fragment that takes a second read to parse, which costs it some clarity.

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 correctly compensates by enumerating the returned fields and their units. For a two-parameter, non-destructive read it covers nearly everything an agent needs, with only error/failure behavior on validation left unstated.

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 both parameters (trade_key with its qbk_ prefix, quote with the BLE-0007 example) are already fully documented. The description adds no further meaning about either parameter, such as what happens with an invalid or non-finalised quote number. Baseline 3 applies since the schema does the heavy lifting.

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 description states a specific outcome: a quote rendered in the exact argument shape of Nero Work's submit_quote tool, validated by Nero Work's own rules. It names the field set (labour_minor, materials_minor, vat_minor in pence, validity_hours, exclusions, notes) and the extras behavior, which distinguishes it from siblings like draft_quote or finalise_quote. It is written as a noun phrase rather than a verb-led sentence, so the action itself comes from the title rather than the description.

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 explicit statement of when to call this rather than draft_quote, finalise_quote, or get_quote, and no prerequisites are given (for example, whether the quote must be finalised first). The Nero Work validation mention hints that this is a pre-submission step, but the agent must infer that. No when-not conditions or alternatives are named.

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