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

With no annotations provided, the description carries full responsibility. It states 'Read-only operation — no side effects, no parameters' which discloses safety, and further details the x402 payment mechanism (HTTP 402 challenge with USDC amount and receiver on Base). This is comprehensive for a status-check tool.

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?

The description is front-loaded with the most critical info (read-only, no params), then lists the return fields, then gives usage guidance, and ends with payment details. Each sentence serves a distinct purpose with no redundancy. It is informative yet efficient.

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?

Since there is no output schema, the description enumerates the returned fields, making the response format clear. It covers purpose, usage, payment, and field names. For a simple read-only status endpoint, nothing essential 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?

The input schema is empty (no parameters), and the description confirms 'no parameters'. While it doesn't add new semantic meaning beyond the schema, it explicitly reinforces the fact, which is helpful for agents that may not infer from an empty schema. Baseline for zero parameters is 4, so this score is appropriate.

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 a specific verb ('Returns') and resource ('service's Telegram integration status'), lists the exact fields, and explicitly differentiates from siblings by naming get_market_stats and get_onchain_sales with their distinct purposes. This leaves no ambiguity about what the tool does.

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?

It provides explicit guidance: 'Use it to confirm this service's own monitoring is alive (and its heartbeat recent) before trusting other outputs', and then names alternatives for other data needs. This is a clear when-to-use and when-not-to-use directive.

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