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 well: it discloses a 20 s rewrite cadence, a 503 refusal (not charged) when data exceeds 120 s, a $0.02 USDC x402 cost per call, and the privacy rule that public channels are named by @username while private chats appear only as counts. It stops short of explaining auth/payment setup or any result-count cap, so it is strong but not exhaustive.

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 resource and bounded window, and there is no filler or hedging across its four sentences. The long enumerated list of returned fields is partly redundant given an output schema exists, which slightly dilutes conciseness, but the density is otherwise justified.

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?

For a two-param, read-only live-feed tool with an output schema, the description covers freshness, refusal behavior, cost, and channel-anonymization semantics – the operational facts an agent actually needs. The main remaining gap is guidance on how it relates to sibling feeds, which leaves selection to inference.

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 both parameters (chain, minutes) are already documented with defaults, enums and bounds; the baseline is 3. The description restates the 1-120 minute window and both chains but adds no syntax, format, or interaction detail beyond what the schema provides.

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 resource precisely: contract addresses surfaced by followed Telegram call chats within a bounded look-back window, along with the derived fields returned. An agent can distinguish it from historical siblings like sol_calls_outcomes or bursts tools by the 'last 1-120 minutes' framing, but the description never names a sibling, so routing relies on inference.

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?

Usage is implied by the 1-120 minute live window and the 'followed Telegram call chats' scope, which tells an agent roughly when this is the right feed. However, there is no explicit when-to-use versus alternatives (e.g. sol_calls_outcomes for settled results, sol_bursts_live for volume spikes) and no stated preconditions such as requiring followed chats to exist.

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