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

Annotations already declare readOnlyHint=true, destructiveHint=false, idempotentHint=true and closed-world, so the safety profile is fully covered without the description's help. The description adds the meaningful behavioral detail that results come newest first. It does not mention the default page size, pagination/has_more semantics, or what happens with zero results, but with complete annotations a 3 is right.

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 sentences, with the resource and sort order front-loaded before the filter enumeration, and no filler. The filter clause is a dense run-on ('binding (bound / unbound / server) or source') that re-lists enum values already in the schema, which is minor 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?

For a seven-parameter, fully documented, non-destructive read tool with no output schema, the description covers what it returns, ordering, filtering, and where to go for detail. The remaining gap is that with no output schema, the agent is not told the shape of a receipt object or how pagination is signalled in the response.

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% and every one of the seven parameters is already documented, so the baseline is 3. The description adds genuine meaning for customer_reference with the dispute/chargeback framing and groups the remaining filters, but it contributes no format or interaction detail beyond the schema for site, source, binding, limit, or starting_after.

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?

Clear verb+resource ('Consent receipts newest first') with an explicit ordering statement, so the agent knows exactly what comes back. It also implicitly distinguishes itself from get_receipt by scoping itself as the list operation, though it never states outright that this is a collection endpoint versus a single-record fetch.

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 parenthetical on customer_reference ('find the receipt behind a disputed subscription or chargeback') gives a concrete use case, and the closing sentence names get_receipt as the alternative for single-receipt detail plus integrity check. No explicit when-not conditions are given, and the boundary with other list endpoints (e.g., list_findings, list_due_notices) is left implicit.

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