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

Annotations already declare readOnlyHint and openWorldHint, so safety is covered; the description adds useful behavioral context by listing the returned public data and scam/fake flags. It also discloses the $0.05 USDC x402 payment path when no API key is used, though it does not describe error behavior or rate 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?

The description is two sentences and front-loads the core lookup behavior before adding the payment condition. Every sentence carries relevant information with no wasted wording.

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 one-parameter lookup with no output schema, the description sufficiently enumerates what is returned: existence, account type, public name, bio, photo, audience size, and scam/fake flags. Combined with the read-only/open-world annotations, it gives the agent enough context to call the tool correctly.

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% and the single required handle parameter is fully documented as a Telegram username without the @. The description reinforces the Telegram context but adds no syntax or format detail beyond the schema, so the baseline of 3 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 Telegram username lookup: it checks existence, classifies the handle as user/bot/channel/group, and lists returned metadata. The Telegram-specific resource clearly distinguishes it from sibling username tools for Discord, Snapchat, TikTok, and generic OSINT scanners.

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 gives no explicit guidance on when to use this tool versus alternatives such as username_scanner or osint-username, nor any when-not conditions. The only conditional context is pricing without an API key, which is not usage guidance.

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