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

Annotations already declare readOnly, idempotent, non-destructive and closed-world, so the safety profile is covered. The description adds genuinely new behavioral context: the hit rates are backward-looking and explicitly 'not a forecast', the 50-graded-position threshold governs ranking eligibility, and the default/ceiling return size is stated.

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?

Front-loaded with the core action and each subsequent sentence carries distinct information (entry fields, thresholds, disclaimer, size). It is dense but every clause earns its place; slightly long, with the tier and field enumeration bordering on output-shape detail.

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 compensates by enumerating the returned fields (handle, platform, tier, graded positions, verified hit rate, recent activity, link) and by stating the ranking caveat and list semantics. Nothing an agent needs to call and interpret this read-only list tool is missing.

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 description coverage is 100%, so sort, limit and section are already fully documented in the schema, including the 'spy' explanation the description never mentions. The description restates the 10-default/50-cap and adds the 50-position threshold for the trusted section, but does not enrich the parameters beyond the schema, so 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?

States a specific verb and resource: it 'ranks the voices with the best verified track record' and enumerates exactly what a voice is (individual authors across X, Reddit, Substack, YouTube, plus crowd sources like a subreddit). This is clearly distinct from the company/strategy/signal siblings, so an agent can route to it without opening a schema.

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?

The description explains the two list concepts (trusted requires 50 graded positions; earning holds voices still building a record), which implicitly tells the agent when each section applies. However, it never states when to reach for this tool versus its siblings, nor any explicit exclusions, so usage is inferred rather than directed.

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