lexware_download_order_confirmation_fileDownload order confirmation PDFs from Lexware Office using the order UUID. Retrieve official documents for record-keeping, sharing, or customer communication.
Download the PDF file for an order confirmation.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Order confirmation UUID |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, indicating a safe, idempotent read operation. The description adds no further behavioral context (e.g., what happens if the ID is invalid or file not found). It does not contradict 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 description is a single short sentence that clearly conveys the tool's purpose. Every word earns its place, with no redundancy.
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?
There is no output schema. The description omits details about the return format (e.g., raw PDF binary) or potential error handling, which would be useful for an AI agent. However, for a simple download tool, the lack of extensive context is acceptable.
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?
The input schema fully documents the single required parameter 'id' with UUID format and description 'Order confirmation UUID'. The description adds no further semantics beyond schema coverage. 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 clearly states the tool downloads the PDF file for an order confirmation. It specifies the verb 'download' and the resource 'PDF file for an order confirmation', distinguishing it from sibling download tools for invoices, credit notes, etc.
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 description provides no guidance on when to use this tool versus alternatives. There is no mention of prerequisites or exclusions. Among siblings with similar download functions, explicit guidance would help an AI agent choose correctly.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.