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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds one genuinely new behavioral fact — results are sorted newest first — but says nothing about pagination, result caps, or whether multiple filters combine.

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?

One short sentence plus a compact filter list, with the sort behavior front-loaded. Nothing is redundant, though the filter fragment is terse enough to be slightly cryptic.

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 three-parameter list tool with no output schema, the essentials are present, but listing tools typically need pagination or result-size context, which is absent. Adequate but with a clear gap for an agent planning a bulk retrieval.

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 0%, so the description must carry the load; it does clarify that q searches number, customer, and process, which the bare schema does not. However, customer_id and billing_document_id are only named, not explained, and AND/OR filter behavior is unstated.

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 names a specific verb and resource ('Lieferscheine auflisten') plus the sort order ('neueste zuerst'), which clearly separates it from get_delivery_note and the create/update/delete siblings. It stops short of explicitly contrasting itself with list_documents or get_delivery_note.

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?

No guidance on when to use this versus get_delivery_note (single record) or list_documents; the agent must infer that this is the bulk-lookup path. Filtering is mentioned but not tied to any use case or exclusion.

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