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

Beyond the readOnly/openWorld annotations, it discloses pagination direction, that empty and terminal pages are not charged, that reactions and media URLs may be absent, and that repeat requests may re-purchase data. The pricing signals are muddled though: 'at least 10 Nexscope credits' conflicts with '1 credit per request' in the pasted pricing block, which could mislead on 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 core is front-loaded and clear, but the body is bloated with pasted documentation: a pricing section, a heading that restates the tool title, and a duplicated cache paragraph plus markdown link already present in the schema. Several sentences repeat structured data rather than earning their place.

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 read-only paginated fetch with no output schema, it covers the essentials an agent needs: paging via cursor, cost implications, caching, missing fields, and unsupported private channels. The internal cost inconsistency is the one real gap.

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%, so all three parameters are already documented. The description restates cursor behavior and pastes the cache_max_age text verbatim from the schema, adding no new semantics; 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 first sentence names a specific verb and resource (retrieves one page of public Telegram channel/group posts) and enumerates the returned fields, so an agent understands the operation immediately. It does not explicitly contrast with siblings like social_telegram_channel or social_telegram_post, so the boundary has to be inferred from 'posts' vs 'channel'/'post'.

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 does give concrete usage cues: 'Pass the returned cursor to fetch the previous page' and 'does not support private or invite-only channels and groups.' However it never states when to choose this over social_telegram_channel or social_telegram_post, which is the main selection decision an agent faces here.

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