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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is covered. The description adds only marginal context beyond that ('Execution: synchronous', 'Task support: forbidden'), while the long orchestration paragraph concerns response presentation rather than tool behavior, so the value added is modest.

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 first sentence is copied verbatim from the title (including a stray double period 'creative..'), so half the text is redundant. The trailing orchestration boilerplate about assistantSummary, raw JSON and ID display is generic padding that dilutes the tool-specific content.

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 not be explained, and the description covers the basic read-only, single-opportunity nature of the call. It is nonetheless incomplete on parameter usage and deprecation handling, and the space it does spend goes to presentation boilerplate rather than tool semantics.

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 0% across four parameters (seatId, seatName, advertiserId, opportunityId), so the description carries the full explanatory burden. It provides no per-parameter meaning at all, only a vague reference to 'the selected advertiser scope', leaving the agent to infer how scope and opportunity IDs interact.

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 ('Get one active or historical World Intelligence opportunity and its compact provenance') plus scope (selected advertiser scope). It also distinguishes itself by declaring it does not publish creative and by naming the canonical sibling get_world_opportunity, though that differentiation is largely a restatement of its alias status.

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?

'Deprecated alias for get_world_opportunity' implicitly steers the agent toward the canonical tool, which is genuinely useful routing. However there is no explicit when-to-use/when-not-to-use framing, no statement of when the deprecated alias is still acceptable, and no condition that selects it over the many other World Intelligence siblings.

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