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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=true, and the description confirms it is a plain GET. It adds useful context on the pending/eligible distinction and the shape of the results, but says nothing about pagination, result limits, or ordering for what is clearly a list endpoint.

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 tight sentences: the resource definition and returned fields come first, then the optional filters. The trailing endpoint path is low value but small, and nothing is padded.

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?

With no output schema, the description compensates by enumerating the returned fields, and all two optional parameters are covered. The remaining gap is list-level behavior (pagination, volume expectations), which is minor for a zero-required-parameter read tool.

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 both parameters are fully documented in the input schema (recipient_id scoping and include_ineligible's default false). The description restates those two behaviors in prose but adds no format, id-source, or default detail beyond the schema — the 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?

Names the specific resource (payouts owed but not yet transferred) and enumerates the returned fields (recipient, program, reward count, total amount). It implicitly separates itself from referralrock_list_payout_transactions by emphasizing 'not yet transferred', but never names that sibling explicitly, so differentiation requires the agent to infer.

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?

'Payouts that are owed but not yet transferred' implies when the tool applies versus a transaction-history listing, and the two optional scoping phrases hint at narrowing use. However, there is no explicit when-to-use, when-not, or named alternative (e.g. list_payout_transactions for settled payouts).

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