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

Annotations cover the safety profile (readOnlyHint=true, openWorldHint=false), and the description adds genuinely new behavior: the PDF uses the account-specific template, contains no prices, and the file is returned base64-encoded. What is missing is failure behavior when the delivery note does not exist or is still a draft.

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 short sentences with zero filler; the content-relevant constraint (no prices) and the return encoding are both front-loaded.

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, the description correctly discloses the return form (base64 file) and template scope. Only error/edge-case behavior and whether the payload is raw base64 versus a data URI remain uncovered, which is minor for a one-parameter read tool.

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% with a single required 'id' already documented as 'Lieferschein-ID', so the schema carries the load. The description adds no further meaning about the identifier, which is acceptable at baseline 3.

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 concrete verb+resource: renders a Lieferschein (delivery note) PDF using the account's template, explicitly without prices. The resource name alone separates it from download_contract_pdf and download_document_pdf, though no sibling is named explicitly.

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 by the resource name — an agent infers 'use this when you need the delivery note as a PDF'. There is no statement of when to prefer it over download_e_invoice_xml or download_document_pdf, and no prerequisites such as the note needing to exist or be finalized.

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