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

Adds genuinely useful behavior beyond the annotations: no authentication/login required, credit-based cost, and a caching contract with a 0-credit cached response. However the cost claims conflict with each other ('at least 10 Nexscope credits' vs '1 credit per request'), which leaves the agent unable to predict what a call will actually cost.

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 text is a pasted documentation block: a marketing sentence ('Telegram Channel Details API View Pricing Get public…'), a duplicated credit statement, and a caching paragraph copied word-for-word from the schema description. The useful scoping and cost facts are buried mid-paragraph rather than front-loaded.

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-parameter read tool with no output schema, it covers what is returned, what inputs are unsupported, that no login is needed, and how caching affects cost and response flags. The only real hole is the unresolved credit-cost contradiction, which leaves a practical unknown for the agent.

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 'handle' and 'cache_max_age' are already documented in the input schema. The description restates the cache semantics verbatim rather than adding new meaning, and adds no format or normalization guidance for the handle beyond what the schema lists.

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 verb and resource ('Retrieves public Telegram channel or group metadata') and enumerates the returned fields (name, description, avatar, verification, subscriber count, media counters). It implicitly separates itself from siblings like social_telegram_channel_posts and social_telegram_post by describing metadata rather than content, but never names those alternatives explicitly.

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?

Gives strong negative scoping: private channels, invite-only groups, numeric IDs, and channels without a public web preview are unsupported, and it clarifies that no logged-in Telegram account is used. It does not, however, tell the agent which sibling to call instead when the goal is posts or a single message.

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