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

Annotations carry no readOnly/destructive hints, and the description does not explicitly state that this is a read-only report or whether it has side effects. It adds the 'Pro' access requirement, but for a report tool with no safety annotations, the description should disclose non-mutating behavior, data scope limits, or performance implications; none are provided.

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 a single dense sentence that front-loads the report contents and ends with the licensing note. It is compact and organized, though the phrase 'every open order past its delivery date with days late' is slightly awkward but still understandable.

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?

The description lists four output components, giving a good sense of return value coverage. However, there is no output schema, no mention of date range defaulting when parameters are empty, no indication of result limits or pagination, and no statement about whether all items are always included. For a multi-section report, this is adequate but not 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 description mirrors the date-range concept already present in the from/to parameters. It does not add details about date format handling, inclusive bounds, default behavior when parameters are omitted, or whether both are required; the schema already carries the essential semantics.

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 ('credited back', 'on order', 'open order past its delivery date') and a clear resource ('billing docs report') with date-range scoping. It enumerates exactly what the report returns and contrasts itself with the free list tools, making it distinguishable from siblings like credit_note_list and purchase_order_list.

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?

The only guidance is 'Pro; the list tools are free,' which is a licensing note rather than a usage rule. It does not explicitly state when to choose this report over the individual list tools, nor does it describe conditions like needing aggregate summaries or wanting all overdue orders in one place.

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