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

Annotations already declare readOnlyHint/idempotentHint true and destructiveHint/openWorldHint false, so the safety profile is covered. The description adds genuine context beyond that: synchronous execution, task support forbidden, advertiser-scoping, and critically that the returned JSON is internal orchestration state rather than user-facing content. That output-handling disclosure is the valuable addition.

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 and execution classification are front-loaded, which is good, but the second half is a long block of user-facing rendering instructions that is verbose and partly restates itself ('no publication authority..' with a doubled period). The rendering guidance is relevant but over-sized relative to the tool-selection information that is missing.

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?

Because an output schema exists, return values need not be explained, and annotations carry the safety profile; the description adds useful orchestration context (sync, no publication authority, present assistantSummary first). But for a 20-parameter tool with zero schema coverage, the complete absence of parameter guidance leaves a meaningful 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, and the description supplies no parameter semantics at all. Terms like 'advertiser-scoped' hint at advertiserId, but the remaining nineteen fields (entity, seatId, locales, targetMarkets, marketContext, etc.) are undocumented in both schema and description, so the description fails to compensate for the coverage gap.

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 resource (advertiser-scoped World Intelligence V3 question with evidence), which is more than a tautology. However it does not differentiate from the crowded world-research sibling set (get_world_research_summary, get_world_research_insights, get_world_research_decision, etc.), so an agent cannot tell precisely which question-shaped artifact this returns without opening the schema.

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 offers response-formatting guidance ('Use assistantSummary first', 'suggest the next best LeanrIQ action') but never states when to call this tool versus the many adjacent world-research getters. There is no when/when-not condition and no named alternative, leaving tool selection entirely to inference.

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