List payments

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

The description adds real behavioral detail beyond annotations: it states the sort order, that paging is caller-driven through start_position and max_results, and the exact loop-termination condition (request until fewer than max_results rows return). It also correctly reinforces the read-only nature of the operation.

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?

Four sentences, each carrying essential information: purpose, sort order, when to use, when to avoid, and the pagination contract. No filler or redundancy; key operational guidance is front-loaded.

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?

The description covers purpose, use conditions, alternative routing, safety profile, and paging behavior. Parameters are fully documented in the schema, and an output schema exists, so nothing critical is missing for correct invocation.

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?

The input schema already documents both parameters thoroughly, so the baseline is solid. The description adds value by explaining how the two parameters work together in a paging loop and when to stop, which is not fully captured in the schema's individual parameter descriptions.

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 clearly states the operation: listing payments, with a specific sort order (most recent transaction date first) and pagination behavior. It also distinguishes itself from search_payments, making the tool's role unambiguous even among many sibling tools.

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?

It explicitly says when to use this tool ('when you have nothing to filter on') and when to prefer the alternative ('prefer search_payments when you can filter by customer or date'). This gives the agent a clear decision rule with no inference required.

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