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

The annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false. The description adds substantial behavioral context beyond that: item fields such as number, kind, status, latest, attachment IDs, stale quotation semantics, seller.complete meaning, and the 409 non-sales-deal error.

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 description is front-loaded but significantly repetitive: the first paragraph and the later 'Sales documents (D149)' paragraph restate the same resource set, fields, attachments, download route, and stale semantics. This duplication wastes space and makes the definition less crisp than it could be.

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?

Although there is no output schema, the description explains the returned item shape, attachment IDs, status values, stale quotation behavior, seller.complete precondition, and error case. For a two-parameter read-only list tool, this gives the agent enough to invoke and interpret it correctly.

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 schema already documents both required parameters with patterns and examples. The description adds only the high-level instruction to give the deal key, not syntax or constraints beyond the schema, so the baseline 3 is appropriate.

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 identifies the exact resource set: quotations, billing notes, and receipts issued for a Sales & Billing deal, newest first, including installments. It is clearly a retrieval/list operation for sales documents, but it does not explicitly contrast itself with the sibling issue_sales_document tool, so it falls short of a 5.

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?

It tells the agent to supply the deal key and documents a 409 when the target is not a Sales & Billing deal, which gives some usage context. However, it does not explicitly say when to choose this tool over get_issue, issue_sales_document, or other related tools, leaving the main selection guidance implied.

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