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

Goes well beyond annotations: clarifies that nothing is charged by this tool, payment happens on Stripe's page, balance/plan updates a few seconds later, the link must be returned verbatim, and auto_reload charges at most once per day. Annotations only carry generic write/openWorld flags, so this context is genuinely additive.

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?

Front-loads the core action, then layers constraints in a logical order. Slightly long with mild redundancy ('NOTHING IS CHARGED' plus 'they pay on Stripe's page'), and the inline `for: "wallet"` quoting is a bit awkward, but nearly every sentence carries operational value.

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 payment-link generator with no output schema, this covers the critical unknowns: no charge occurs here, settlement timing, link handling, the alternate switching/cancelling page returned for existing subscribers, and per-branch parameter meaning. Nothing needed to invoke it correctly is missing.

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%, so baseline is 3, but the description adds meaning beyond the terse schema strings: the $5/$10/$25 wallet amounts, the Manage/Autopilot plan naming and monthly pricing, and the once-a-day auto-reload semantics. It stops short of explaining what happens if `plan` is omitted alongside `for: "plan"`.

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+resource (get a Stripe checkout link) and scopes it to exactly two purposes (wallet load or plan purchase), making it clearly distinct from siblings like connect_stripe_for_payments, my_wallet, or set_my_account_type.

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 branch logic for `for: "wallet"` vs `for: "plan"`, prerequisite behavior (existing paid-plan members are not switched), a condition for auto_reload ('only when the member has clearly asked'), and a constraint ('never ask for or accept card details').

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