List payments

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

Annotations already declare readOnlyHint and openWorldHint. The description adds useful behavior beyond those annotations: results are scoped to the organization, ordered newest first, optionally filtered, and paged with a total count. It does not discuss permissions or rate limits, but the notable behavioral traits are disclosed.

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 compact sentences with the core listing scope and ordering front-loaded, followed by filtering and paging details. Every sentence adds useful information without repetition.

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 read-only list tool with full parameter schema coverage and annotations, the description provides enough to call it correctly: scope, ordering, filters, and paging behavior. It could be slightly more complete by naming when to choose it over get_payment_history, but the core operational context is present.

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 all five parameters are already documented in the schema. The description adds a high-level summary of filtering by status, chain, or creation date and mentions paging, but does not add syntax or format details beyond the schema.

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 specific verb and resource: listing payments scoped to the API key's organization, with ordering and filters. It is clear what the tool does, though it does not explicitly differentiate itself from siblings like get_payment_history.

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?

Implies usage through mention of optional filters and paging, but gives no explicit guidance on when to use this versus get_payment, get_payment_history, or get_summary. The agent can infer it is for browsing payments, but alternatives are not addressed.

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