List checkout sessions

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is fully covered. The description adds nothing on top: no mention of default page size, cursor-based pagination behavior, or how results are ordered, even though both cursor parameters exist in the schema.

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 opens by repeating its own first sentence verbatim, which is pure waste. The remaining sentence is tight, but the duplication means it is not front-loaded cleanly.

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 six parameters, a nested date-range object, and cursor pagination but no output schema, the description should at least explain paging and default result size. It covers only two of the six filters and says nothing about the returned collection shape.

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 all six parameters, including the nested created range object and the two cursors, are already documented in the schema. The description restates the status and payment_link filters without adding format, interaction, or default semantics beyond that baseline.

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 a specific verb and resource ('List checkout sessions'), so an agent immediately knows the operation. However, it does not differentiate itself from siblings like get_checkout_session, create_checkout_session, or expire_checkout_session, which would have raised this to a 5.

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 offers no when-to-use guidance or exclusions relative to the sibling read tools (get_checkout_session, get_checkout_session_by_reference). The mention of filtering by status or payment_link is parameter guidance, not selection guidance.

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