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

Annotations already mark the operation as read-only, idempotent, and non-destructive. The description adds useful behavioral context by disclosing that the result is a download link valid for one hour and by describing the rendered document's contents. No contradiction exists between the description and annotations.

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 main description is a single, front-loaded sentence containing the essential facts: what to call, what it produces, and the link expiry. The trailing 'Pro.' fragment is unexplained and does not earn its place, but it does not seriously impair comprehension.

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 simple read-only tool with both parameters documented in the schema, the description adequately covers the output format, content, and link expiry. The odd 'Pro.' suffix introduces slight ambiguity about a possible access requirement, and there is no explicit note on error behavior, so it is not quite a 5.

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%, so the schema already documents id and out_path. The description's 'return a download link valid for one hour' largely echoes the out_path schema description rather than adding new parameter-level meaning, so it stays at the baseline.

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 starts with a direct command: 'Call this tool to render one quote as an A4 print-ready document', clearly naming the verb, resource, and deliverable. It also specifies the output contents (invoice layout, validity date, acceptance block) and the one-hour download link, which distinguishes it from siblings like quote_get, quote_list, or quote_report.

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 opening 'Call this tool to render one quote...' gives an explicit trigger, and the PDF-specific language implies it is for print/download use rather than retrieval or acceptance workflows. It stops short of naming alternatives or stating when not to use it, so it is clear but not fully exclusive.

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