List all payouts

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=true, so the safety profile is fully covered by structured data. The description adds only that results are paginated, which is genuinely useful context but thin. No mention of rate limits, ordering defaults, or empty-result behavior.

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?

A single front-loaded sentence with no padding or repetition; it is efficient. It is arguably undersized relative to a ten-parameter filtering tool, but conciseness itself is not violated.

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 ten optional filter parameters, no output schema, and no annotation-level detail about the response, the description leaves the return shape and filtering capability to inference. The rich schema and annotations cover most needs, but a sentence about filtering and pagination limits would round it out.

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 each parameter is already documented in the schema, including the advanced filter syntax on group_id and the tenant_id precedence rule. The description adds nothing beyond the schema, making the baseline 3 correct.

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 (retrieve) plus resource (payouts) and scopes it ('for your partner program'), so an agent immediately knows this is a read/list operation over payouts. It does not differentiate from any sibling, but no other payout-listing sibling exists, so the gap is minor. Clear but generic.

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?

There is no when-to-use guidance, no mention of the filtering/pagination use cases the ten parameters enable, and no named alternative or exclusion condition. The agent must infer usage entirely from the schema. Only the bare operation is described.

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