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

Annotations already cover the safety profile (readOnlyHint, idempotentHint, destructiveHint=false, openWorldHint=false), yet the description adds genuinely new behavior: synchronous execution, task support forbidden, and explicit result-handling rules (use assistantSummary first, never surface raw JSON, mention IDs only for debugging). It correctly aligns with the readOnly annotation rather than contradicting it.

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 deprecation status are front-loaded, but the lead sentence repeats the title verbatim (including a stray double period), and the resulting block mixes identity, execution metadata, and a long style guide. Useful content is present but padded.

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 re-explained, and the read-only/synchronous behavior is covered. But for a 20-parameter tool with zero schema documentation, the description leaves the caller unable to determine what any input means or which combinations are meaningful, which is a substantial 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?

The schema has 20 properties with 0% description coverage, so the description carries the full burden — and it adds essentially nothing about parameters. It implies advertiser scoping (loosely mapping to advertiserId) but never explains entity, eventId, question, limit, locale fields, or the nested marketContext/marketLanguageProfile objects.

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 concrete verb+resource (reads advertiser-scoped World Intelligence V3 insights) and scope, and labels itself a deprecated alias. However, it never tells the agent that the non-prefixed get_world_research_insights exists or which one to prefer, so differentiation from the sibling alias is left to inference. The opening sentence is also a verbatim duplicate of the title.

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?

There is no explicit when-to-use or when-not-to-use guidance. Marking itself 'deprecated alias' implies the agent should route elsewhere, but no replacement tool or condition is named. The bulk of the text is output-formatting policy, not selection guidance.

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