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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is fully covered. The description adds the ordering behavior, which is genuine value, but says nothing about paging; the caller only learns the legacy-bare-array vs {items, next_cursor} distinction from the parameter 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?

A single short sentence with the resource and the ordering front-loaded. There is no wasted language and nothing is buried.

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?

No output schema exists, and the description does not describe return shape (bare array vs items/next_cursor envelope) or whether any filtering is possible. For a simple read-only list tool whose schema carries the paging contract this is adequate, but the envelope behavior is important enough that the description could reinforce it.

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 limit and cursor are already documented in detail, including the unusual first-page behavior. The description contributes nothing about parameters, which meets the baseline for full coverage.

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 and resource ('List your invoice_payment rows') and adds a useful ordering guarantee ('newest first'). It does not explicitly differentiate itself from invoice_payment_read or invoice_list, 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?

There is no when-to-use guidance, no mention of prerequisites or scoping, and no pointer to the sibling tools (invoice_payment_read, invoice_payment_record, invoice_payment_delete) that an agent must choose between. Usage is only implied by the name and the word 'List'.

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