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

Annotations already establish readOnly, idempotent, non-destructive, and closed-world, so the safety profile is covered. The description adds genuine behavioral context beyond that: the payload is a live aggregated snapshot spanning five named sections, and 'big wins just banked (realized profit)' clarifies that profit figures are realized rather than unrealized. It does not cover freshness/refresh cadence or result-size limits.

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 leads with the resource and then enumerates the return sections, followed by a short purpose cue. The enumeration is dense but each clause maps to a distinct section of the response, so little is wasted; it could be broken into a list for faster scanning.

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 parameters and no output schema, the description carries the burden of telling the agent what the response contains, and it does so by naming all five sections. Remaining gaps are minor: no indication of snapshot freshness, result caps, or whether sections are always populated.

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?

There are zero input parameters, so there is nothing for the description to disambiguate; the baseline applies. The description's per-section framing is the only semantic content needed here.

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 concrete verb-object ('Live Polymarket activity') and enumerates the five constituent feeds (big wins, sharp-money moves, biggest recent trades, trending markets, consensus divergence), so an agent knows exactly what comes back. It stops short of distinguishing itself from close siblings such as polyrank_get_movers, polyrank_get_top_roi_trades, and polyrank_get_smart_money_report, whose subject matter overlaps with individual sections here.

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 closing line ('Good for "what are the big and sharp wallets doing right now"') supplies a real usage cue tied to a user intent. However, given at least three siblings cover overlapping slices, the absence of any explicit 'use this instead of X when Y' guidance leaves the agent to guess which overlapping tool to pick.

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