listCheckoutSessions

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

With no annotations provided, the description carries the full behavioral disclosure burden. It explicitly discloses that the operation is read-only, names the HTTP method, and states a concrete rate limit of 100 requests per minute. It does not cover pagination or default limit behavior, but the disclosed traits are meaningful and go beyond 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 is concise and front-loaded: it states purpose first, then rate limit, then read-only/HTTP method. Every clause adds useful information with no filler or repetition.

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 low-complexity tool with one optional parameter, the description covers the core purpose and important behavioral constraints, so a no-argument call is reasonably supported. However, it leaves the 'limit' parameter semantics and the response shape to inference, which makes informed use of the optional parameter incomplete.

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?

The input schema has one parameter ('limit') with 0% description coverage, and the description does not mention it at all. The agent receives no information about what the limit controls, its default, maximum value, or units, so the description fails to compensate for the schema gap.

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 action and resource ('List recent Checkout sessions') and clarifies the endpoint ('GET /paygate/connect/checkout/sessions'). This clearly distinguishes it from sibling list tools focused on other resources such as listTransactions or listCustomers.

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 purpose line implies when to use it (when recent Checkout sessions are needed) and the 'Read-only' wording signals a safe retrieval operation. However, it does not explicitly contrast this tool with sibling list tools or state when not to use it, so usage guidance is only implied rather than explicit.

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