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

With no annotations, the description carries the full burden; it does state 'Read-only', which is a genuine safety disclosure, and hints at return contents (recordings URL, duration). It says nothing about pagination, message ordering, or result size limits — meaningful gaps for a message-history tool that can return large volumes.

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 compact sentences, front-loaded with the scope and followed by the behavioral note. No filler and nothing redundant.

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?

There is no output schema, and the description partially compensates by mentioning message content and call metadata. However, pagination, ordering, and volume/rate behavior — the practical concerns for a chat-history read — are omitted, leaving the agent unable to anticipate result shape beyond a hint.

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 both required parameters (agent id, chat id) are already documented with sources in the schema. The description adds no additional meaning about the parameters, so the 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?

States the resource precisely ('all messages of one Telegram chat') and adds a distinguishing trait (voice-call turns with recording URL and duration) that separates it from list_telegram_chats or get_telegram_analytics. It lacks an explicit verb, but 'read' comes from the title and the operation is unambiguous.

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 no when-to-use or when-not guidance and never names an alternative such as list_telegram_chats (for enumerating chats) versus this tool (for reading one chat's history). The only routing hint lives in the schema param descriptions, not the description itself.

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