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

Annotations already declare readOnlyHint=true, so safety is covered. The description adds real value beyond them by disclosing the returned field set and the presence of lexwareAppUrl, a link that opens the record in Lexware Office — an unusual side-output an agent should know about. It does not cover auth or not-found behavior.

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, front-loaded with the resource and result shape, ending with the endpoint. Nothing redundant and no filler.

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 read-only single-resource fetch with no output schema, the description usefully compensates by listing the returned sections. The only gap is error/not-found behavior and any pagination or embedding options, which are minor here.

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?

There is a single parameter with 100% schema description coverage, including a UUID pattern and the note that the id comes from lexware_list_vouchers. The description says only 'by id' and adds no format or sourcing detail beyond the schema, so the baseline 3 applies.

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?

Names a precise verb and resource ('Get one order confirmation by id') and enumerates the payload it returns: status, line items, totals, delivery terms. The resource name alone separates it from the many sibling getters (get_invoice, get_delivery_note, get_quotation), and the endpoint snippet confirms the exact REST path.

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 implied: fetch a single order confirmation when you have its id. The description gives no explicit when-to-use or when-not guidance, and does not name alternatives such as lexware_list_vouchers (the schema description carries that routing hint instead). Adequate but leaves selection logic to inference.

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