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

Annotations already cover readOnly/idempotent/non-destructive, and the description adds genuinely new behavior: the required `payments:read` scope, the cursor round-trip protocol for paging, and a security note that free-text content arrives under `untrusted_fields` and must not be treated as instructions. That last point is a valuable, non-obvious operational constraint an agent could not infer from structured fields.

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?

Three short sentences, front-loaded with purpose, then auth, then paging, then the safety note. Every sentence carries distinct information and none restates the title or annotations.

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 simple two-parameter read tool with no output schema, this covers the essentials: scope, paging, and the shape/trust level of free-text fields. Minor gaps remain — no hint at default page size, sort order, or what a transfer record contains beyond the untrusted text — but nothing blocking 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?

Schema description coverage is 0%, so the description must carry parameter meaning. It explains `cursor` precisely (feed the returned cursor back to page) but says nothing about `limit` — its range (1-100), default, or unit of measure — leaving half the parameters undocumented in both places.

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 states a specific verb and resource ('List my payouts'), which usefully maps the tool name 'transfers' to the user-facing concept 'payouts'. It does not, however, distinguish this from the many sibling list/get tools such as get_transfer, get_payout_summary, list_payments, or list_received_payments.

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 implied use case is clear (enumerate payouts), and the pagination instruction ('Pass the answer's cursor back as cursor for the next page') gives concrete follow-up guidance. But there is no explicit statement of when to choose this over get_transfer for a single item or get_payout_summary for aggregates, which are the obvious alternatives.

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