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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered. The description adds genuinely useful behavior beyond that: results are ordered most recent first, they are paginated, and all amounts are normalized to USD, which matters because a per-record currency field is returned.

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 set: purpose and ordering are front-loaded, then the returned fields, then the currency caveat. The long field enumeration earns its space because there is no output schema, though the run-on list slightly hurts scanability.

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 the returned fields and status/type vocabularies and notes pagination meta, which is exactly the burden it must carry. Minor gaps remain around total-count/next-page semantics and whether canceled or pending items are included by default.

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% and both parameters (page, page_size with defaults and max) are fully documented in the schema. The description only alludes to pagination generically, adding no format or default detail beyond what the schema already provides, so the baseline of 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 precise verb and resource ('List the authenticated customer's payment history') plus ordering and scope, which cleanly separates it from list_invoices, list_refunds and list_orders by resource alone. It never names or contrasts a sibling explicitly, so it stops short of the top tier.

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 only implied: the phrase 'authenticated customer's payment history' tells the agent this is the account-scoped payment listing, but there is no when-to-use statement, no mention of prerequisites beyond implied auth, and no routing against list_invoices/list_refunds.

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