stripe_checkout_session

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

No annotations are provided, so the description carries the full burden of behavior disclosure. 'Generate' implies an external side effect—creating a real Stripe Checkout session—but the description does not disclose that this likely requires a valid API key, makes a network call, or returns a session URL. It also does not mention whether trial days are a Stripe-specific behavior or how the session is finalized.

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 one concise sentence that front-loads the primary action and resource, then lists the key inputs. Every phrase contributes useful information, and there is no repetition of schema content.

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 an external billing action with seven parameters, no annotations, and no output schema, the description is underspecified. It does not explain what the tool returns (e.g., a Checkout session URL), what authorization is required, or how it relates to subscription flows. An agent could create a Checkout session but would not know how to consume the result or handle failures.

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 the schema already provides meaning for every parameter. The description adds only a high-level summary, matching success_url/cancel_url and trial_days but providing no syntax, format, or usage details beyond what the schema contains. Baseline 3 is appropriate.

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 uses a specific verb, 'Generate,' and a specific resource, 'Stripe Checkout session,' and names the core features: line items, success/cancel URLs, and optional trial periods. This differentiates it from sibling billing tools like stripe_subscription_manager and stripe_webhook_handler because it is clearly about creating a checkout session rather than managing subscriptions or handling webhook events.

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 explicit guidance on when to use this tool versus stripe_subscription_manager or other billing tools. There is no mention of one-time payments, subscription vs checkout scenarios, or exclusions. The intended use must be inferred from the tool name and description, which is not sufficient for a billing context with closely related siblings.

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