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

Annotations already declare the mutation/idempotent/open-world profile, and the description adds real behavioral context beyond them: the buyer must open the returned checkoutUrl, and the campaign is only booked after a verified native Stripe payment webhook (i.e., completion is asynchronous and not guaranteed by the call itself). It does not mention rate limits or what happens if the checkout expires.

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?

Three short sentences, front-loaded with the action and scoping constraint, then the next step, then the completion condition. Every sentence earns its place with no filler.

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 10-parameter write tool with an output schema and full annotations, the description covers the essential flow an agent needs: what is created, that the checkoutUrl must be opened, and that booking is confirmed only via webhook. Return-value detail is delegated to the output schema, so nothing critical 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 50%, so the schema documents reviewedAmount, advertisementId, idempotency_key, reviewedCurrency and reviewedSelection but leaves quoteId, quoteIds, bookingIds, providerLineIds and reviewedSubtotalUsd unexplained. The description reinforces that the reviewed* fields must match the reviewed quote, but adds no syntax or meaning for the five undocumented parameters.

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 for a campaign) and scopes it precisely to the 'exact campaign and total the buyer reviewed', which implicitly separates it from prepare_campaign_booking. It never names a sibling tool outright, so an agent must infer the ordering from the word 'reviewed'.

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 phrase 'the exact campaign and total the buyer reviewed' implies this must be called after prepare_campaign_booking with matching reviewed values, and 'Open the returned checkoutUrl' implies the post-call step. However, there is no explicit when-to-use/when-not guidance and no named alternative, leaving the prerequisite chain to inference.

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