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

Annotations already declare read-only/idempotent/non-destructive, so the classification line is partly redundant; but 'Execution: synchronous' and 'Task support: forbidden' add real behavior. The output-handling rules (never display raw JSON, prefer assistantSummary, mention IDs sparingly) go well beyond any structured field and meaningfully shape agent behavior.

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 first sentence is essentially a restatement of the title (including a stray double period), and the middle metadata ('Classification... Execution... Task support...') is flat. The presentation guidance is useful but arrives undifferentiated rather than front-loaded.

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, and the presentation guidance is genuinely helpful. But for a 20-parameter tool with zero schema coverage, the complete absence of any parameter explanation leaves the definition inadequate 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?

Twenty parameters with 0% schema description coverage, and the description documents none of them (entity, question, targetMarkets, seatId, advertiserId, etc. are never explained). With the schema carrying no descriptions, the description had to compensate and instead says nothing about any parameter.

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?

The description states a specific verb and resource ('Read advertiser-scoped World Intelligence V3 insights with evidence'), which is more informative than the bare name. However, it never distinguishes itself from the many related siblings (get_world_intelligence, get_world_research_summary, get_world_research_decision, leanriq_get_world_research_insights), so an agent cannot tell which of these overlapping 'insights' readers 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?

The description contains no when-to-use or when-not-to-use guidance and names no alternative tool. Its instructions ('use assistantSummary first', 'suggest the next best LeanrIQ action') govern how to present results, not when this tool should be selected over its siblings.

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