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

Annotations already declare read-only, idempotent, openWorld=false, non-destructive. The description adds value beyond them: 'Execution: synchronous', 'Task support: forbidden', 'no publication authority', and explicit downstream-orchestration rules about assistantSummary, raw JSON masking, and mention IDs. It does not cover pagination, ordering, or evidence shape, keeping it from a 5.

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 body mixes classification, execution mode, and presentation policy into a run-on sequence, includes a stray double period, and repeats itself ('LeanrIQ and ChatGPT orchestration'). Functional but not tightly edited.

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, but with 20 optional parameters at 0% coverage and no selection guidance against ~10 similar research-read siblings, the definition leaves major gaps for a complex query tool.

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 no enum hints; the description explains none of them. entity, question, advertiserId, targetMarket, marketContext, locale fields, and the various *Locale arrays are entirely undocumented, so the agent has no basis for choosing or formatting inputs.

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 mentions with evidence), and the title adds the scoping constraint 'no publication authority.' It does not differentiate itself from the many sibling get_world_research_* tools (insights, events, decision, summary, etc.), so an agent cannot tell from the text alone which of these it should 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?

The description offers output-handling instructions (use assistantSummary first, never show raw JSON) but says nothing about when to invoke this tool versus alternatives like get_world_research_insights or get_world_research_events. No preconditions, no exclusions, no selection criteria.

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