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

Annotations already declare readOnlyHint=true and openWorldHint=false, so the safety profile is covered. The description adds useful behavioral context by describing the payload (per-network share counts plus discussion threads from Hacker News, Lobsters and Lemmy), but says nothing about ordering, aggregation across the window, or result limits beyond what the schema implies.

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 sentence that packs the resource, the returned fields, and the discussion sources with zero filler. Nothing could be removed without losing information.

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 must carry return-value information, and it does so by naming titles, per-network share counts and discussion sources. Minor gaps remain around sort order and pagination behavior, but the essentials for deciding to call it are present.

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%: 'domain' and 'window' carry their own descriptions with examples and allowed values, and 'limit' is self-explanatory via default 25 and 1-100 bounds. The description contributes no additional parameter meaning, so the baseline 3 applies.

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 a specific resource — 'most-shared URLs across networks' — and enumerates the returned fields (titles, shares per network, discussions), which clearly separates it from topic- or mention-oriented siblings. It stops short of explicitly contrasting with social_trending_topics, so it is clear but not fully differentiated.

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 choose this over social_trending_topics, hot_discussions, or social_top_mentions, and no statement of exclusions or prerequisites. The agent must infer the use case entirely from the return-content phrasing.

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