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

Annotations already declare readOnly, idempotent, non-destructive and openWorld=false, so safety is covered. The description still adds real context beyond them: the result set is scoped to the 'current buying context' and the auth failure path is interactive (the customer is asked to sign in on printdash.io), which changes how an agent should sequence the call. It stops short of describing pagination or empty-list behavior.

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?

The payload is front-loaded in the first clause and every sentence carries information the agent needs. It is slightly padded by the repeated qualifier 'as the Quotes list shows it' used twice for status and total, which could have been stated once.

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 one-parameter read tool with an output schema, this covers the important unknowns: auth requirement, context scoping, and the fields returned. It would be complete at 5 if it named set_context as the way to change the buying context or said what an empty list means.

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 the limit parameter is fully documented there (1-20, default 10, newest first). The description adds nothing about the single parameter, so the schema does all the work and 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?

The description names a concrete resource (saved quotes) and enumerates exactly what each row carries: status, total including delivery, expiry and link. It is clearly the list counterpart to get_quote, but it never names a sibling or says explicitly how it differs from get_quote or list_quote_requests, leaving that inference to the agent.

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?

Usage is only implied: 'in the current buying context' hints that results depend on a context set elsewhere (set_context), but that dependency is never stated. The one genuine usage prerequisite is spelled out well — a signed-in Printdash account is required and the connection will prompt the customer to sign in. There are no when-not-to-use cases or named alternatives.

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