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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so the safety profile is fully covered without the description. The description adds the notable detail that it reads the *exact current* state and includes creative readiness, which is real behavioral value beyond annotations, but there is no mention of auth needs, staleness, or cost of the call.

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?

A single sentence with no filler, and the most decision-relevant element (the review-before-payment context) is placed at the end where it frames the whole call. Nothing is repeated from the title or schema.

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?

An output schema exists, so return values need no explanation, and the read-only/idempotent annotations mean the low-risk profile is adequate. The remaining gap is guidance on selecting among quoteId, quoteIds.owned/partner, bookingIds and providerLineIds, which neither the schema nor the description explains.

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 only 20% (only advertisementId is described) across five parameters, including a nested quoteIds object and three ID-list parameters whose relationship is unexplained. The description mentions no parameters at all, so it fails to compensate for the coverage gap that the rubric requires it to fill.

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 (read) and a concrete set of returned facts (selections, total, currency, creative readiness), and the 'before payment' framing separates it from create_campaign_checkout and preview_campaign_plan. It is clear but packs several noun phrases into one clause rather than crisply defining the resource.

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?

'For the buyer to review before payment' implicitly places this in the pre-checkout step of the flow, which is useful sequencing context. However, no sibling is named (create_campaign_checkout, preview_campaign_plan, get_campaign_status are all plausible alternatives), so the agent must infer when to prefer this tool.

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