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

With no annotations, the description carries the full burden and does so richly: caller anonymity via sha1 hashes, chat names exposed only for public channels/groups, hourly rebuild cadence, 503 refusal (uncharged) when data is older than 3h, and a $0.05 USDC x402 charge per call. These are exactly the operational facts an agent needs before invoking.

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 identity ('Telegram call-channel callers ... ranked by ...'), followed by metric definitions, privacy rules, windows, and cost. Dense and single-paragraph, but each clause contributes operational information; only the lengthy metric enumeration risks being a run-on.

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?

An output schema exists, so return shape needn't be explained. For a paid, periodically rebuilt data tool the description covers pricing, staleness/refusal behavior, anonymization, and scoring windows — nothing an agent needs to call it correctly 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 coverage is 100% so baseline is 3, but the description goes further by defining the metrics that the sort enum values refer to (e.g., win35 = '+35% before -20%', hit15 = '+15% within 60 min', rug = '-80% within 60 min'). This gives the enum options meaning the schema alone does not convey.

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 precise verb+resource: 'Telegram call-channel callers ... ranked by what happened after their own posts', with the exact metric set (hit15, win35, x2, rug rate, median returns). This is clearly distinguishable from siblings like sol_calls_live, sol_calls_outcomes, and sol_wallet_leaders.

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 names the available windows and the ranking basis, implying when the tool is useful, but never says when to prefer it over sol_calls_live, sol_calls_outcomes, or the wallet leaderboard tools. No exclusions or alternative-selection guidance is given.

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