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

The annotations already declare a safe read-only, non-destructive, open-world operation. The description adds useful behavioral context: the required scope, the endpoint, and the pagination contract where next_offset should be passed back as offset. It stops short of describing error behavior or rate limits.

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?

The description is short and front-loaded with the core action, then adds filtering, scope, endpoint, and return/paging details. Most sentences earn their place, though the raw endpoint reference is marginal for an agent.

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?

With no output schema, the description appropriately explains that the tool returns count, total, next_offset, and items, and it explains how to page. Given complete schema coverage and annotations, this is nearly complete, though it could mention other filter/sort options at a high level.

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 all seven parameters are already documented by the schema. The description only restates contact_id filtering and the next_offset-to-offset paging relationship, which the schema also covers, so it adds little beyond the structured fields.

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 states a specific verb and resource: list delivery notes. It also names the supported filters and the endpoint. It does not explicitly distinguish itself from the sibling get_delivery_note, but the list-versus-get distinction is clear enough from the name.

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?

It says the tool can filter by contact_id or a JSON filter and notes the required delivery_note scope. However, it never states when to use this list tool instead of get_delivery_note or other list endpoints.

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