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

Annotations only declare readOnlyHint=true; the description adds the material behavioral fact that the MCP session is anonymous and cannot subscribe anyone, so the tool is purely informational. That is exactly the kind of context annotations cannot convey. It stops short of noting trial/PRO gating mechanics beyond the marketing summary.

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?

Two sentences, with the useful enumeration of channels/bot/deep link up front and the constraint last. The first sentence is dense with parenthetical detail (RU/EN, extreme events, PRO, 3-day trial) but each item maps to a real capability the user may ask about, so little is wasted.

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-optional-parameter informational tool with an output schema, the description covers what is explained, what is linked, and what the tool cannot do. Return values need not be described given the output schema. Only minor gaps remain, such as how the deep link behaves when coin is omitted.

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%, with both coin and lang already documented including an example and the enum. The description reinforces the coin parameter's purpose ('opens the bot with the coin already set'), which adds slight framing but no syntax or defaulting detail beyond the schema. 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 states concretely what the tool returns: an explanation of the public Telegram channels (RU/EN, extreme-events, delayed), the personal bot with instant alerts, and a deep link pre-filled with a coin. The closing clause 'this tool only explains and links' makes it clearly not a data-fetching tool, separating it in spirit from data siblings like funding_events, though no sibling is named.

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?

Framing as 'How to get funding alerts from the radar' plus the explicit exclusion of subscribing tells the agent the right situation (user asks about alerts/delivery) and one thing this tool cannot do. Alternatives such as radar_about or funding_events are not referenced, so routing is implied rather than spelled out.

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