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

Annotations already cover read-only and open-world, yet the description adds real value: the channel must be public, results include view counts, ordering is newest first, and each call costs 1 credit. It does not disclose paging limits or what a post object contains, but the additions are substantive.

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?

Two short sentences, zero filler, with the core scope leading and ordering plus cost appended. Nothing is redundant or buried.

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 full schema coverage and no output schema, the description covers scope, ordering, and cost. The remaining gap is return-shape detail (which fields besides views a post carries), which for a simple paginated list is a minor omission.

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%, with handle formats (@handle or t.me URL) and cursor provenance documented in the schema itself. The description adds only the "newest first" ordering hint that informs cursor use, so baseline 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?

States a concrete resource and scope: "a public channel's latest posts with views, newest first." An agent knows it is a listing operation, not a single-post fetch, though it never names the sibling tools (telegram_channel, telegram_post) that it differs from.

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?

Usage is implied by "latest posts" (list a channel's recent content) but there is no explicit when-to-use, when-not, or pointer to telegram_post for a single post. The agent must infer routing from the noun phrase alone.

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