payouts.list

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

No annotations are provided, so the description carries the full burden. While 'List' implies a read-only operation, the description fails to disclose pagination behavior, sorting behavior, or what data is returned. It doesn't address rate limits, idempotency, or safety characteristics.

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?

The single sentence is appropriately front-loaded with the verb and contains no redundant information. However, brevity crosses into underspecification given the tool's complexity with 6 parameters including pagination controls.

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 tool with 6 parameters (including pagination cursors and timestamp ranges) and no output schema or annotations, the description is inadequate. It omits essential context about date filtering, pagination mechanics, and return values that an agent needs to invoke the tool correctly.

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?

With 0% schema description coverage across 6 parameters, the description must compensate significantly. It only implicitly references 'account' (accountId) but provides no context for startTimestamp/endTimestamp, ascending, limit, or startsAfter, leaving critical pagination and filtering parameters undocumented.

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 uses a specific verb ('List') and resource ('Ryft payouts'), and correctly scopes the operation to 'an account' (matching the required accountId parameter). However, it doesn't explicitly distinguish this from sibling tool payouts.get (single retrieval) or mention the date-range filtering capability evident in the schema.

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 description provides no guidance on when to use this list operation versus payouts.get, nor does it explain the pagination workflow (limit/startsAfter) or timestamp filtering. It lacks prerequisites or conditions for use.

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