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

Annotations already declare readOnlyHint=true and destructiveHint=false, and the description's 'Read only' is consistent with them. It adds the enumerated response fields, but says nothing about pagination continuity, result size, or the open-world scope, so with annotations carrying the safety profile a 3 is appropriate.

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 dense sentence that front-loads the core action and then the returned fields, with 'Read only. GET /payments.' as terse supporting facts. Every clause carries information; no padding.

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?

With no output schema, the description usefully enumerates what a payment record contains, which is exactly the gap that needs filling. Pagination mechanics are handled by the schema, so the only remaining soft spot is the absence of guidance on narrowing results via date/customer filters.

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 page, sort, filter, start_date/end_date, customer_id, per_page and updated_after are all documented in the schema itself. The description adds no syntax or semantic detail beyond that, matching the baseline for schema-covered parameters.

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?

Specific verb+resource ('List payments received') with an enumeration of the returned fields (customer, date, amount, unapplied balance, method, reference, matched/voided status), which lets an agent distinguish it from the singular invoiced_get_payment. Sibling differentiation is implicit rather than stated explicitly, 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?

Usage is implied by 'List payments received' and the read-only framing, but the description never states when to prefer this over invoiced_get_payment or how the date/filter parameters select a subset. No explicit alternatives or exclusions are given.

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