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

No annotations exist, so the description carries the full burden. It does disclose freshness ('real-time') and that rates are 'confirmed', which is genuine behavioral context beyond the schema. It omits the auth/permission implications of the token and what happens when quotes are still pending or expired.

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?

A single well-formed sentence with the purpose front-loaded and zero filler. Slightly dense with stacked qualifiers ('3-venue', 'client token') but nothing is wasted.

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 and no annotations, the description is the sole source of return-value and safety information. It conveys the conceptual return (status + confirmed rates) but not the shape of a 'pending' vs 'confirmed' response, nor any auth or rate-limit expectations for a live status check.

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 100%, and the schema itself documents the clientToken with a format example ('cqt_...'). The description only restates 'using the client token' without adding syntax, sourcing, or failure semantics, so 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 ('Check') and resource ('status and confirmed rates for an existing 3-venue quote request'), making it distinguishable from request_curated_quotes which creates the request. It never explicitly names the sibling it complements, so an agent must infer the pairing from 'existing'.

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?

The phrase 'for an existing ... quote request' implies this is a follow-up to requesting quotes, which is useful context. However, it gives no explicit when-to-use/when-not guidance, no polling advice, and no named alternative among siblings like request_curated_quotes or whoami.

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