platformFees.getRefunds

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While 'List' implies a read-only operation, the description fails to disclose pagination behavior, filtering capabilities, what data is returned, rate limits, or authorization requirements. It mentions the domain (Ryft platform fee) but no operational constraints.

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 description is extremely concise at 7 words, front-loaded with the action verb, and contains no redundancy or filler. However, it errs on the side of under-specification rather than optimal information density, lacking necessary context that would make it truly effective.

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?

Given 0% schema coverage, no annotations, and no output schema, the description is insufficiently complete. A single sentence cannot adequately document the parameter purpose, return structure, and behavioral characteristics needed when structured metadata is absent. The description should compensate for the lack of schema descriptions but does not.

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%, placing full burden on the description. The phrase 'for a Ryft platform fee' implies the 'id' parameter refers to a platform fee identifier, but the description does not explicitly document the parameter name, expected format, or that it is required. It adds minimal semantic value beyond the schema structure.

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' with a clear resource ('refunds for a Ryft platform fee'). It implicitly distinguishes from sibling platformFees.get (which retrieves the fee itself) and paymentSessions.refund (which likely creates refunds) by focusing on listing refunds for a specific platform fee. However, it lacks explicit differentiation stating that this is a retrieval operation versus the creation operation in paymentSessions.

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 tool versus alternatives, prerequisites for use (e.g., needing a valid platform fee ID first), or when not to use it. There is no mention that this retrieves existing refunds rather than creating new ones.

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