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

Annotations already declare read-only, idempotent, closed-world, non-destructive, so the safety profile is covered. The description adds genuinely new behavioral context beyond the annotations: result ordering ('newest first') and cursor-based pagination, both of which affect how an agent consumes results.

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?

One compact sentence plus a fragment, both front-loaded with the most important information (resource, scope, ordering) before the secondary pagination note. No filler or repetition of the title.

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 three-parameter, read-only list tool with no output schema and full schema coverage, the description covers resource, ordering, filtering, and pagination. The main omission is that no valid status values are given, which matters because the parameter has no enum.

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%, so the baseline is 3, and the description still adds some meaning by confirming the status filter is optional and that the listing is cursor-paginated. It does not add format details beyond the schema (e.g., valid status values, since there is no enum), leaving a small gap.

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 ('Payouts of the account') and adds scope ('newest first, optionally filtered by status'), which clearly separates it from get_payout and create_payout. It does not explicitly name the sibling list tools it must be distinguished from, but the resource is specific enough to select the right tool.

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 implied rather than stated: 'of the account' tells the agent this is the account-wide listing rather than a single-payout lookup, and 'optionally filtered by status' hints at the filtering alternative. There is no explicit when-to-use vs. when-not, and no mention that filtering by payout ID requires get_payout.

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