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

Annotations only declare readOnlyHint=false, openWorldHint=false, and idempotentHint=true, but the description adds substantial context beyond that: session-state preservation requirements, the token-based retry path, the recommendation not to drop to raw HTTP, the prohibition on collecting card details via chat, and the two-phase call sequence. This is rich operational disclosure that the annotations alone do not convey.

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 purpose is front-loaded, but the body is a dense run-on that packs multiple distinct instructions into single sentences (session preservation, retry token, UI render confirmation, fallback). Most content earns its place, yet the lack of structure makes it harder to parse than necessary.

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 multi-phase, mutating payment tool this is thorough: it covers prerequisites, both call modes, UI-render confirmation, retry behavior, and the fallback path. An output schema exists, so return-value detail is not needed, and the description does not leave a functional gap.

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% and each parameter is already well documented, including the either/or constraint between payment_collection_requested and the setup_intent_id/payment_method_id pair. The description adds sequencing ('After successful Stripe setup, call this same tool again with setup_intent_id and payment_method_id') but largely reinforces what the schema already states, so it sits at the baseline 3.

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 opens with a specific verb+resource+scope: 'Prepare secure Stripe payment collection or submit the resulting payment method during the consumer-prefill umbrella post-choose flow.' This clearly distinguishes it from siblings like umbrella_consumer_attach, umbrella_consumer_bind, and umbrella_consumer_select, and an agent can tell what the tool does without opening the schema.

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?

It states explicit preconditions ('Use this only after Coverage Cat says payment_needed'), ordering ('First call it with payment_collection_requested: true'), exclusions ('do not send the shopper straight to payment_url', 'do not request card details through conversational text'), and fallback routing ('if UI support is unknown or unsupported... share payment_url with the specific fallback reason'). Nothing is left to inference.

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