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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint=false and destructiveHint=false, so 'Classification: read-only' and 'no publication authority' mostly restate them. The description does, however, add genuine non-schema context: the payload is internal orchestration state, assistantSummary should drive the reply, and raw JSON/IDs should be surfaced only on request.

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 opening clause duplicates the title and the 'Classification/Execution/Task support' triplet largely echoes annotations, with a stray double period. The response-handling sentences are useful but generic boilerplate, so the text is longer than the information it carries.

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 described. But with 20 optional parameters, 0% schema coverage and no statement of what identifies an event or advertiser-scope, the definition is not sufficient for an agent to construct a valid, successful call.

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?

There are 20 parameters at 0% schema description coverage, no enums and nested objects (marketContext, marketLanguageProfile), and the description explains none of them. It never indicates that eventId, advertiserId, entity, targetMarket or the locale/market objects mean, nor which combination is needed to resolve an event.

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+resource ('Read ... World Intelligence V3 event') with scope ('advertiser-scoped') and a distinguishing qualifier ('with evidence'). However it never separates this tool from the near-identical sibling get_world_research_events (plural) or from get_world_intelligence/get_world_activation_evidence, so an agent cannot tell which retrieval to pick.

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?

No when-to-use, when-not-to-use, prerequisites, or alternative routing is provided. The only 'use ... first/never/prefer' sentences concern how to phrase the answer to the user, not which tool to select, so selection guidance is effectively absent.

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