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

Annotations already declare readOnlyHint=true, so safety is covered, and the description adds real value beyond that: which fields come back (status enum values, expiration, line items, totals) and the lexwareAppUrl deep link. The underlying endpoint GET /v1/quotations/{id} further anchors the behavior. It does not discuss pagination or empty/error behavior, but for a single-record fetch that is minor.

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?

Front-loaded with the core action and the returned payload in one tight sentence; the endpoint token is arguably redundant but aids debugging. No filler or restated title.

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, so the description must carry the return-value burden, and it largely does by naming the key fields and the deep link. Combined with rich annotation and schema coverage, an agent has enough to call this correctly; only edge-case behavior is unaddressed.

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 single id parameter is fully described there (including its UUID pattern and the list_vouchers provenance). The description only echoes 'by id' and adds no format or sourcing detail beyond the schema, so the baseline of 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?

States a specific verb and resource ('Get one quotation by id') and enumerates what the response contains (status, expiration date, line items, totals). This cleanly separates it from sibling getters for invoices, credit notes, and delivery notes, though it never names a sibling directly.

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: retrieving a single quotation by id after it has been listed. There is no explicit statement of when to prefer this over lexware_list_vouchers or how the id is obtained (that hint lives in the schema, not the description). No exclusions or prerequisites are given.

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