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

No annotations are supplied, so the description carries the full behavioral burden. It usefully discloses the matching logic ('matches settlements by payer wallet address across your fleet'), which explains how rows are derived, but says nothing about read-only safety, pagination behavior, ordering, or what the records contain.

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 front-loaded sentences with the scope stated first and the matching behavior second; there is no redundant filler. Some internal jargon ('FortFi', 'fleet') costs a little clarity for outside agents.

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 two-parameter, annotation-free read tool with full schema coverage and no output schema, the description conveys what is listed and how rows are matched. The main shortfall is absent guidance on default ordering/paging or the shape of a purchase record.

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 (limit, walletMappingId) are fully documented in the schema. The description adds only a loose hint that filtering relates to payer wallet addresses, without mapping it to walletMappingId or explaining limit semantics, so 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?

The description names the resource concretely ('FortFi checkouts your vaults paid') and frames it as the 'Buyer view', which implicitly distinguishes it from the sibling list_payment_sales seller view. It stops short of naming that sibling explicitly, so an agent must infer the pairing rather than read it.

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 'Buyer view' framing suggests this is the buyer-side counterpart to sales, but there is no explicit when-to-use statement, no when-not, and no named alternative. An agent can guess the intent but has no routing rule.

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