Read recent Telegram messages

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

No annotations are provided, so the description must fully disclose behavior. It states read-only and mentions the output format and parameter overrides (since_id overrides last_n). However, it does not disclose potential rate limits, auth requirements, or what happens if no media messages are found.

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 description is extremely concise, consisting of two functional sentences plus a standalone 'Read-only.' It is front-loaded with the main action and every sentence adds value without redundancy.

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?

Given no output schema, the description adequately explains the return format and the two primary use cases. It does not define 'media messages' or mention error handling, but it is otherwise complete for a read-only tool with clear parameters.

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%, baseline 3. The description adds valuable context beyond the schema: explains the difference between last_n and since_id, notes that since_id overrides last_n, and describes the output format compact objects. It also implies the chat parameter can be id or @username, matching the schema.

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 exports recent media messages from a single chat, using a specific verb ('Export') and resource ('recent media messages from one chat'). It distinguishes from siblings like tg_chats (which lists chats) and tg_download (which downloads files).

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 explicitly explains when to use last_n vs since_id (incremental reads). It says 'Read-only' but does not specify when not to use this tool or mention alternatives like tg_download or tg_status for other operations.

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