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

With no annotations, the description carries the full behavioral burden and does useful work: it discloses the ordering, as-at date semantics, count categories, and that the tool is 'Free'. It does not explicitly state read-only/no side effects, but 'List' plus the absence of mutation language makes that reasonably clear.

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 two tight sentences with the core verb/resource front-loaded and each clause carrying information: ordering, output fields, date, filters, and cost. There is no filler or repetition.

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 five-optional-parameter list tool with no output schema, the description plus the high-coverage schema provides enough to invoke it correctly. It names the returned client/currency/counts and the as-of behavior, though it could be strengthened by mentioning pagination or pointing to delivery_schedule_get for a single schedule.

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 every parameter already has a clear description. The tool description reinforces the client/reference/state filter concepts but adds little meaning beyond the schema, so the baseline 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?

The description opens with a specific action and resource, 'List schedules', and adds distinctive scope and ordering details: 'oldest reference first', 'client, currency and counts as at a date', and filterable states. This clearly separates it from the get/create/delete siblings even though no sibling is named.

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?

There is no explicit guidance on when to choose this list tool over delivery_schedule_get, late_report, or the other siblings. The filtering and listing language implies use for multiple schedules, but no when-not or alternative direction is provided.

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