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 real content by enumerating the returned signals (30-day baseline comparison, spike, lexicon tone, discussions), but says nothing about ordering direction, result caps, or refresh cadence for a ranked feed.

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 front-loaded clause with the resource first and the metrics after the colon; no filler, no restatement of the tool name. It is a fragment but reads cleanly as a one-line spec.

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 metric list does useful work describing what the ranking exposes. Still missing for a ranking tool is how ties/ordering work and what 'discussions' contains, leaving the agent with a partial picture of the payload.

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 67%: 'type' and 'window' carry their own allowed-value lists, while 'limit' documents only bounds and a default. The description contributes nothing about any of the three parameters, so it neither compensates for the gap nor harms — roughly baseline for this coverage level.

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 names the resource ('stocks and crypto assets') and the ranking criterion ('ranked by social attention'), plus the metrics behind the rank (mentions vs 30-day baseline, spike, lexicon tone, discussions). That is enough to separate it from per-symbol siblings like social_symbol_mentions, though no sibling is named explicitly.

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 and no named alternative. An agent must infer from the phrase 'ranked by social attention' that this is the leaderboard-style tool, and gets no steer on choosing between it, social_symbol_mentions, or social_trending_topics.

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