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

Annotations already cover read-only, idempotent, non-destructive, and openWorld=false, and the description partly duplicates them ('Classification: read-only'), which earns no credit. It does add genuine behavioral context: results may be partial, it never publishes creative, opportunities are recommendations, and it discloses an orchestration contract (assistantSummary-first, no raw JSON).

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 statement is front-loaded, which is good, but the rest is a pile-on of orchestration rules and metadata restatement, including a duplicated period ('creative..'), a typo ('LeanrIQ'), and annotation-derived facts that occupy space without adding information.

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-value explanation is not required, but the definition still leaves the three undocumented, all-optional parameters ambiguous and gives no routing guidance among the many intelligence siblings. The response-handling rules are the strongest part; the invocation side is thin.

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?

All three parameters (seatId, seatName, advertiserId) have 0% schema description coverage, and the description says nothing about any of them — not which to prefer, not whether they are filters or selectors. The only mild signal is implied advertiser scoping in the opening sentence. This is a substantial gap the description fails to compensate for.

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 ('Get the latest advertiser World Intelligence summary') and adds scope qualifiers ('fresh, source-backed context that may be partial', 'never publishes creative') that help separate it from run_world_intelligence and get_world_opportunity. It does not explicitly name those siblings, so it falls short of a 5.

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 gives clear guidance on how to USE the result ('Use assistantSummary first', 'Never display raw JSON'), but never says when to call this versus run_world_intelligence, get_world_opportunity, or list_world_signals. Usage is implied rather than stated, which is the definition of a 3.

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