listCheckouts

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It only restates the list action without detailing pagination, idempotency, rate limits, or return format. The minimal text adds no behavioral insight beyond the tool name.

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 a single 6-word sentence, which is under-specified rather than concise. It fails to provide any value beyond the tool name, wasting the opportunity to inform.

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 3 pagination parameters, no output schema, and no annotations, the description is severely incomplete. It does not indicate result structure, pagination behavior, or required authorizations, making it inadequate for reliable tool invocation.

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 schema has 3 parameters (limit, ending_before, starting_after) with 0% description coverage. The tool description does not explain these parameters or their function (e.g., pagination cursors). The description adds no meaning beyond the schema, which itself is empty.

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?

Description states 'Retrieves a list of checkout objects' with a specific verb and resource. It clearly distinguishes from other list tools by resource name (checkout vs charges, events, etc.), but lacks scope or filtering context that would further differentiate.

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 on when to use listCheckouts versus sibling tools like listCharges, listEvents, etc. The description does not mention context, prerequisites, or alternatives, leaving the agent without decision support.

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