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

Annotations already cover the safety profile (readOnlyHint, destructiveHint=false, openWorldHint), so the bar is lower. The description still adds real context beyond them: the required auth scope and the underlying endpoint shape, which tells an agent this is a scoped read against a specific invoice.

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?

Three short sentences, front-loaded with what the tool returns, then prerequisites, then the endpoint. No filler and no repetition of the title.

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 3-parameter filtered list with no output schema, the definition covers purpose, scope requirement, and endpoint. The main gap is that it doesn't describe the shape of the returned payment records, but annotations and the fully documented paging parameters cover most of what an agent needs to call it correctly.

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%, with limit, offset, and invoice_id each carrying their own descriptions (defaults, maxes, and next_offset paging hint). The description adds nothing about parameter syntax or semantics, 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?

States a specific verb-in-effect (retrieves) and resource (payments recorded on one invoice), which is clearly narrower than sibling list tools like smallinvoice_list_invoices. It doesn't explicitly name a sibling to route against, but the scoping to a single invoice makes the distinction obvious.

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?

Usage is implied by 'recorded on one invoice' plus the required invoice_id, and the description adds a prerequisite ('Needs the "invoice" scope'). There is no explicit when-to-use or when-not guidance relative to get_invoice or other list tools, so it stops at implied context.

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