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

Annotations already declare readOnly/idempotent/non-destructive, but the description adds real context: synchronous execution, no publication authority, and that the returned JSON is internal orchestration state that should be summarized via assistantSummary rather than displayed raw. This meaningfully exceeds what the annotations provide.

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?

Purpose is front-loaded, but the text contains a duplicated period ('authority..') and is padded with generic orchestration boilerplate (never display raw JSON, mention IDs, suggest next action) that likely repeats across sibling tools rather than being specific to this one.

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?

The output schema means return values need not be explained, and the description covers read-only behavior and presentation. But for a 16-parameter tool with zero schema coverage and nested objects, the absence of any parameter or scoping semantics leaves a material gap for correct invocation.

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 16 parameters, so the description must carry the burden and it adds nothing about any parameter. It does not explain eventIds (the sole required field), the scoping fields (seatId, advertiserId, targetMarket), or the several locale/market fields whose relationships are non-obvious.

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 ('Read scoped verified event attestations') and adds a scope boundary ('no publication authority'), so an agent can distinguish it from mutation siblings like launch_creative_campaign. However, it never names which sibling to use instead, and the phrase 'Studio approval and activation' is jargon the agent must infer.

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 description gives response-formatting instructions but no when-to-use/when-not-to-use guidance relative to alternatives. 'No publication authority' implies a boundary but does not tell the agent when to call get_world_activation_evidence versus get_world_research_event or get_world_research_events.

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