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

readOnlyHint=true already declares the safety profile, so the description carries a lighter burden. It adds genuine value beyond the annotation by disclosing the content shape (status, line items, shipping conditions) and the presence of lexwareAppUrl deep-link, which matters when no output schema exists.

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 tight sentences with the core action front-loaded, followed by return content and the REST path. Nothing is wasted, though the trailing 'GET /v1/delivery-notes/{id}' is mildly redundant given the tool name and schema.

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 single-param read tool with readOnlyHint and no output schema, the definition covers what it needs: the resource, the key input, the returned fields, and the deep-link field. Only the absence of explicit when-to-use guidance keeps it from being fully complete.

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% and the single id parameter is fully documented with its UUID pattern and provenance ('from lexware_list_vouchers'). The description adds nothing beyond 'by id', so the baseline 3 is appropriate when the schema does all the work.

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 delivery note by id') and even lists the content returned (status, line items, shipping conditions), so an agent can identify it immediately. It doesn't explicitly differentiate itself from the numerous other lexware_get_* siblings, but the resource name is distinct enough to separate it.

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: fetch a single delivery note by id. There is no when-to-use framing, no mention of prerequisites, and no routing to or from alternatives like lexware_list_vouchers, which is referenced only as a source of the id in the schema.

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