get_checkout

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

With no annotations provided, the description must convey behavior. It states 'retrieve', indicating a read-only operation, but doesn't discuss error handling (e.g., invalid ID) or permissions. While the behavior is partially clear, additional context like idempotency or potential null results would improve transparency.

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 sentence with no unnecessary words. It efficiently conveys the tool's purpose and required input, maintaining a front-loaded structure that is easy to scan.

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 the tool's simplicity (one required parameter, no output schema), the description adequately covers the core action. However, it could be more complete by explicitly stating the return format (e.g., 'Returns a checkout session object'), though the verb 'details' implies that.

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 coverage is 100% (one parameter well-described as 'Checkout session ID'). The description adds no extra meaning beyond the schema, simply restating that retrieval is by ID. Thus, it meets the baseline but doesn't enhance parameter understanding.

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 clearly states the action 'Retrieve' and the resource 'checkout session details by ID'. It distinguishes itself from siblings like create_checkout, get_customer, etc., as it specifically targets retrieving a checkout session using its unique ID.

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 implies usage when needing to fetch checkout details by ID, but it lacks explicit guidance on when not to use it or alternatives. For instance, it doesn't mention that to list all checkouts, one would need a different tool, nor does it explain prerequisites.

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