Read a Telegram message discussion

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

Annotations already indicate readOnly, idempotent, and non-destructive behavior, but the description adds valuable context beyond them: 'Does not mark read,' the linked-group comment behavior, and cursor-based pagination. No contradictions with annotations.

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 compact sentences, each earning its place: purpose, linked-group nuance, and pagination/read behavior. Information is front-loaded and there is no fluff.

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 moderate-complexity tool with an output schema and strong annotations, the description covers the important behavioral nuances: pagination, linked-group replies, and no mark-read. It could be more complete by explicitly explaining the input parameters, but the schema supplies names and defaults.

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 0%, so the description must compensate, but it only meaningfully explains the cursor via 'Follow next_cursor for older messages.' It does not clarify chat_id, message_id, or limit semantics beyond what their names imply.

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 clearly states the tool reads the reply thread/comment discussion of a message, which is a specific verb+resource. This distinguishes it from siblings like telegram_get_message (single message) and telegram_get_chat_history (flat chat history) even without naming them.

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?

The description gives clear context for when to use the tool, including handling channel comments that may belong to a linked group and following next_cursor for older messages. It does not explicitly name alternatives or exclusion cases, so it stops short of a full when/when-not comparison.

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