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

Annotations already cover safety (readOnly, idempotent, non-destructive, closed-world), and the description adds genuinely new behavioral context: 'no publication authority', synchronous execution, 'Task support: forbidden', and detailed response-handling rules (use assistantSummary first, never surface raw JSON, mention IDs only when useful). That is meaningful disclosure beyond the annotations, though it says nothing about pagination or failure modes.

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 purpose and deprecation signal are front-loaded, and the response-format instructions are useful, but the first sentence duplicates the title verbatim and even carries a doubled period ('authority..'), a clear redundancy. The block of output-style directives is long for what it conveys, so structure is adequate but imperfect.

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 behavioral guidance is solid. But for a tool with 20 undocumented parameters, nested objects, and 0% schema coverage, the description leaves an agent with almost no information on how to construct a valid call, which is a major completeness gap.

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 with 0% schema description coverage, including nested objects like marketContext and marketLanguageProfile, and the description does not mention a single parameter, its meaning, or how entity/seatId/advertiserId/targetMarket relate. With no schema coverage to lean on, the description fully fails to compensate.

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 advertiser-scoped World Intelligence V3 events with evidence') and explicitly labels itself a deprecated alias for get_world_research_events, which distinguishes it from the canonical sibling. The scope qualifier 'no publication authority' further narrows the purpose. It falls short of 5 because the opening sentence merely restates the title verbatim rather than adding independent information.

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 'Deprecated alias for get_world_research_events' note implies an agent should prefer the canonical tool, and 'no publication authority' signals a usage boundary. However, there is no explicit statement of when to call this alias versus get_world_research_events, nor any prerequisite context, so the guidance is implied rather than stated.

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