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

Annotations only declare readOnlyHint and openWorldHint, but the description adds substantial behavioral context: the five-independent-account privacy threshold, one contribution per account/topic/day, rounding rules, null semantics for no_results_percent, exclusion of anonymous searches, and how stale/unavailable data is represented. It also warns that topic text is untrusted data and never instructions, which is important operational guidance.

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 is front-loaded in the first sentence and every subsequent sentence carries real semantic content rather than filler. It is a dense wall of prose, however, and the privacy/rounding rules would be easier to scan as a short list.

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?

With no output schema and no parameters, the description must carry the full burden, and it does well by defining the key field (no_results_percent), its null cases, and data staleness semantics. It never sketches the overall response shape (e.g., the topic list), so a little is left to discovery.

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 tool takes zero parameters, so there is no parameter semantics to explain and the baseline of 4 applies. The description correctly implies there is nothing to pass.

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 and resource: discover aggregated needs from Agorean searches over the last 30 complete UTC days. It distinguishes this from a raw search tool by framing it as automatically generated, privacy-reviewed topics. It stops short of naming the sibling `search`/`searchJobs` tools it could be confused with, so differentiation is implicit.

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, and no alternative is named. The agent can infer this is for aggregate trend discovery, but nothing tells it whether to prefer this over `search` or what question it answers that a plain search does not.

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