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

Annotations already declare readOnlyHint=true and openWorldHint=false, so safety is covered. The description adds value by enumerating returned content (mentions per network, expected count, spike, trend, first seen, hourly breakdown) — important since no output schema exists — but it omits how a 'spike' or 'trend' is derived and whether results are cached or rate-limited.

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?

A single dense sentence with no filler, and the key scoping detail (one hashtag, cross-network) is front-loaded. It reads as an output list rather than a task statement, which slightly hurts readability, but nothing is wasted.

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, the description does the necessary job of sketching the return shape. But for a two-parameter analytics tool with seven sibling social_* tools, the absence of any selection guidance and the unresolved window-versus-24h ambiguity leave real gaps.

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?

Schema coverage is 100%, so 'tag' and 'window' are already fully documented with examples and allowed values. The description adds no meaning beyond the schema and in fact introduces ambiguity: it states results are 'the last 24 hours by hour' while the window parameter defaults to '1h', leaving the interaction between the two unexplained.

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 identifies the resource ('One hashtag across networks') and enumerates the metrics returned, so the subject is recognisable. However, it is a noun phrase with no verb — it never says whether the tool retrieves, computes or reports the trend — and it does not name a sibling it differs from, leaving the agent to guess against social_symbol_mentions or social_history.

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 when-to-use or when-not-to-use guidance at all, no mention of alternatives among the many social_* siblings, and no prerequisites. The agent is left to infer the tool's role purely from the field list.

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