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

Beyond idempotentHint/openWorldHint, description discloses real behavior: external Stripe payment, idempotent reuse ('Repeating the same quote reuses its order'), and the caution 'Creating checkout is not proof of purchase.' No contradiction with annotations.

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?

Four sentences, zero filler; the critical precondition is first, then return values and caveats. Every sentence earns its place.

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 two-parameter mutation tool with no output schema, description covers preconditions, return shape, idempotency, payment security, and status caveat. It equips an agent to call correctly and avoid common mistakes.

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 covers 100% of parameters with detailed descriptions, so baseline 3 applies. Description reinforces quote context and reuse but adds no new parameter-level syntax or formatting.

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?

Description opens with 'Create or resume Stripe hosted checkout for a quoted 4K license', a specific verb and resource, and adds return value ('checkout URL and private order token') that separates it from retrieval/quote siblings.

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?

Explicit precondition: 'Call ONLY after the user explicitly approves...' and 'never collect card details in chat' clarifies when not to proceed. However it doesn't name sibling alternatives like get_4k_order or quote_4k_license, so exclusions remain implicit.

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