paymentSessions.list

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 but fails to mention pagination behavior (despite limit/startsAfter parameters), date-range filtering capabilities (despite timestamp parameters), or what data is returned. Does not clarify if this is real-time or cached data.

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?

While brief (4 words), this is under-specification rather than efficient conciseness. The single sentence communicates almost nothing beyond the tool name itself, failing to earn its place by providing actionable context.

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 6-parameter tool with 0% schema coverage and no output schema, the description is materially incomplete. It omits critical context about pagination, filtering, return structure, and error conditions required to use the tool effectively.

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% for 6 parameters (timestamps, pagination, account filtering). The description adds no information about parameter semantics, formats, or relationships (e.g., that startTimestamp/endTimestamp create a range), leaving all inputs 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 'List Ryft payment sessions' restates the tool name (tautology) and fails to distinguish this tool from siblings like paymentSessions.get (single retrieval) or paymentSessions.listTransactions (child resource listing). It mentions 'Ryft' (the provider) but adds no scoping details.

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?

No guidance provided on when to use this listing tool versus paymentSessions.get for specific session retrieval, or how to handle pagination with the limit/startsAfter parameters. No prerequisites or filtering logic is explained.

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