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

readOnlyHint=true already covers the safety profile, but the description adds valuable non-annotation context: the returned fields (totals, paid/pending amounts, due dates, status) are disclosed despite there being no output schema. It does not mention auth needs, rate limits, or pagination semantics beyond cursor params in the schema.

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 dense but front-loaded sentences with no wasted filler; the document scope comes first, filters second. The trailing 'OfficeRnD: GET /payments' is a minor endpoint breadcrumb that earns little but does no harm.

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 14-parameter read-only list tool with no output schema, the description covers the resource scope and the returned field set, which is what an agent needs to select and interpret it. Pagination and cursor behavior are delegated to well-documented schema fields, so nothing critical is missing.

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 14 parameters are already documented. The description names the filterable fields and adds an example ('overdue invoices') that maps the date filters to a real scenario, but adds no syntax or format detail beyond the schema. Baseline 3 is appropriate.

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 ('List') and resource ('billing documents — invoices, credit notes, overpayments'), enumerating the document types so it is clearly distinguishable from siblings like list_contracts or list_memberships. An agent knows exactly what set of records this returns.

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?

Gives clear usage context by enumerating filterable dimensions and an example use case ('overdue invoices'), which tells the agent when this tool is appropriate. It stops short of naming alternatives or when-not-to-use conditions, but no sibling overlaps this billing-document resource.

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