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

With annotations already covering read-only/idempotent/non-destructive/closed-world, the description adds real context: synchronous execution, that 'Task support: forbidden', that the JSON is internal application-state for orchestration, and that output must be rendered through assistantSummary rather than shown raw. These are behavioral facts the annotations do not carry.

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?

Front-loaded purpose is good, but the opening sentence duplicates the title and the 'Classification/Execution/Task support' fragment reads as raw boilerplate. The remaining sentences are output-formatting rules that, while useful, pad the description without adding selection or parameter value.

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-shape explanation is not required, but for a 20-parameter tool with nested objects and zero schema descriptions the definition leaves invocation under-specified. It is complete on rendering policy but not on how to construct a valid call.

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?

With 20 parameters (nested objects, locale/market/language fields) at 0% schema coverage and 0 required, the description carries the entire burden of explaining them and says nothing about any parameter. The agent cannot tell what 'entity', 'seatId', 'marketContext', or 'languageVariantGroupId' mean or which are needed.

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') plus resource ('World Intelligence V3 profile') and scope ('advertiser-scoped') with a distinct qualifier ('with evidence'). However, the first sentence merely duplicates the title verbatim, and it offers no differentiation from the many parallel siblings (get_world_research_decision, get_world_research_summary, get_world_intelligence, build_world_research_profile).

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 guidance on when to call this tool versus the cluster of related get_world_research_* tools or get_world_intelligence. The only instructions concern how to phrase the response to the user, not when to select this tool; 'no publication authority' hints at a limitation but is not a usage rule.

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