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

Adds substantial behavior beyond annotations: user completes payment on Stripe, rate-limited polling of get_account_usage (≥15s apart, max 8), retry-once semantics after credits arrive, and no-silent-purchase guarantee. However it references a 'preparedRequestId' that does not exist in the schema (the param is requestKey), leaving the retry contract ambiguous.

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?

Purpose is front-loaded in the first clause and each subsequent sentence adds a distinct operational constraint (precondition, polling budget, retry). Slightly dense procedural prose, and the stray 'preparedRequestId' term is a wasted/confusing token.

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 6-param, 5-required, open-world mutation with no output schema, the description covers preconditions, user-facing flow, polling limits, and retry behavior well. The notable gap is what the tool returns (a checkout URL/identifier) and how kind/locale affect the result.

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 0%, so the description must carry parameter meaning; it partially does by implying offer comes from get_account_usage offers and that interval is the recurring billing interval. It says nothing about kind (subscription vs pack), locale, or the idempotency role of requestKey, and confirmed is only indirectly implied.

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?

States a specific verb and resource ('Create a Stripe checkout link for this connected account') plus a distinguishing scope clause ('without website sign-in'). It also explicitly delimits what it is not ('Does not charge a saved card or open the billing portal'), separating it from other billing-related actions.

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?

Gives explicit sequencing ('First get_account_usage...'), a precondition ('Call only after the user explicitly chooses the offer'), a prohibition ('Never purchase silently'), and negative boundaries ('Does not charge a saved card or open the billing portal'). Alternatives and when-not-to-call are both covered.

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