Channel Details

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

Annotations are thin (readOnly=false, openWorld=true, idempotent=false, destructive=false), so the description carries real weight: it discloses the public-web-preview mechanism, that no logged-in account is used, that it consumes paid credits and requires confirm=true, and that the read-like POST does not publish anywhere. It notably pre-explains why a read operation carries readOnlyHint=false.

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?

Three front-loaded sentences: purpose, mechanism, limitations, then cost/safety. Efficient with little waste, though the trailing 'Read-like POST requests do not publish to social platforms' is slightly boilerplate.

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?

With no output schema and full schema coverage, the description supplies the mechanistic context (public preview, no login), the cost/confirm gate, and the unsupported-input list. Complete enough to invoke correctly; only the absence of alternative routing leaves a small 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 description coverage is 100%, so the schema already documents handle, account, confirm, and cache_max_age. The description reinforces the confirm=true and credit-cost behavior but adds no format or syntax detail beyond the schema, so the baseline of 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?

States a specific verb and resource (retrieves public Telegram channel/group metadata) and enumerates exactly what's returned: name, description, avatar, verification status, subscriber/member count, media counters. This clearly distinguishes it from siblings like telegram_channel_posts and telegram_post_details.

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?

Explicitly states the exclusions — private channels, invite-only groups, numeric IDs, and channels lacking a public web preview are unsupported — which tells the agent when this tool will fail. It does not, however, name a sibling alternative to use in those cases, so it stops short of full when/when-not routing.

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