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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the description's real contribution is the auth behavior: it requires a signed-in Printdash account and the connection triggers a sign-in prompt on printdash.io when absent. That is genuinely useful context an agent cannot get from the structured fields, though error behavior for an unknown request number is unstated.

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. The returned-field inventory comes first and the prerequisite second, so an agent can decide to call before reading the auth caveat.

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 an output schema present the description needn't detail return shape, and it still summarizes the payload while covering the auth prerequisite for a one-parameter read. Only the failure mode for an invalid or unknown request number is left implicit.

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 parameter already documents 'request number (or the request id from its link)'. The description restates 'by its request number' without adding format, resolution, or fallback detail, 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 and resource ('one custom quote request by its request number') and enumerates what it yields: request contents, status, cancellability, and the resulting quote. That single-vs-list framing cleanly separates it from list_quote_requests without needing the sibling's 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?

The 'one ... by its request number' phrasing implies the lookup use case, but no alternative is named (e.g. list_quote_requests for browsing, cancel_quote_request for acting on it) and no when-not condition is given. Usage is inferable rather than stated.

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