lexware_deeplink_delivery_noteRetrieve a direct link to view or edit a specific delivery note in Lexware web app by providing its UUID, enabling quick access without manual navigation.
Get a direct link to view/edit a delivery note in the Lexware web app.
| Name | Required | Description | Default |
|---|---|---|---|
| id | Yes | Delivery note UUID |
Changes observed during successful MCP inspections.
v3.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true, destructiveHint=false, and idempotentHint=true. The description adds 'view/edit' which clarifies the link's purpose but does not disclose additional behavioral traits beyond the annotations. No contradiction found.
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, concise sentence that effectively communicates the tool's purpose. It is front-loaded and contains no extraneous information, though it could be slightly expanded for completeness.
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 tool with one parameter, full schema coverage, and thorough annotations, the description provides sufficient context. It explains the output (a direct link) and the tool's intent, without needing to detail return values since there is no output schema.
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 single parameter 'id' is fully documented in the schema with a description ('Delivery note UUID') and format constraints. The description adds no further meaning beyond the schema, so a baseline score of 3 is appropriate given 100% schema coverage.
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 returns a direct link to view/edit a delivery note in the Lexware web app. It uses a specific verb ('Get') and specific resource ('direct link to view/edit a delivery note'), distinguishing it from sibling tools like lexware_get_delivery_note (returns data) or lexware_download_delivery_note_file (downloads file).
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 implies use when a deep link to a delivery note is needed, but does not explicitly state when to use this versus alternative tools such as other deeplink tools (e.g., lexware_deeplink_invoice). No exclusions or contextual guidance is provided.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.