delivery_notes_list

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds useful domain context (what a delivery note represents) but says nothing about pagination behavior, default ordering, or result size beyond what the schema states.

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 sentences, no waste: the operational summary comes first and the domain definition second. Nothing redundant.

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 list tool with full schema coverage and complete annotations, the description supplies the missing 'what is a delivery note' context. Only minor gaps remain, such as default page size or ordering, which the schema partially covers.

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%, so every parameter including the status enum and date formats is already documented. The description only echoes the filter categories ('status, date range, client, and search term') without adding syntax or semantics, which is the baseline case.

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+resource ('List delivery notes') plus the scope (selected company) and the available filters, so an agent can distinguish it from delivery_notes_get/create/update. It never explicitly contrasts itself with the sibling delivery-note tools, so it stops short of a 5.

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 by 'list ... with optional filtering' and by the domain sentence explaining what a delivery note is, but there is no explicit when-to-use / when-not guidance or pointer to alternatives such as delivery_notes_get for a single record.

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