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

No annotations are provided, so the description carries the full disclosure burden, yet it says nothing about the six operation modes, read-only nature, rate limits, pagination, or what 'response_mode' compact vs full means. Only the verb 'search/aggregate' weakly implies a read operation.

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?

One short sentence with no waste, but the brevity comes at the cost of under-specification rather than tight expression. It is not front-loaded with anything actionable.

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 needn't be explained, but for a tool with a complex nested payload, six operations, and zero annotations, the description leaves the agent without the operational context needed to invoke it correctly.

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 single top-level parameter is a deeply nested payload with ~16 fields and six-valued operation enum, and schema description coverage is 0%. The description never mentions 'payload' or any operation, so it contributes essentially no meaning beyond the structured schema.

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 verb ('search and aggregate') and a broad resource ('public content, sentiment, and trends'), but the scope is fuzzy and it never distinguishes itself from overlapping siblings like trend-data, keyword-data, or the social-* search tools. It reads more like a category label than a distinct operation.

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?

No when-to-use guidance, no prerequisites, and no mention of which sibling to prefer for a given task. With 33 siblings that include several trend and social-search tools, this omission forces the agent to guess.

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