List scheduled Telegram messages

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

Annotations already establish readOnly, idempotent, and non-destructive behavior. The description adds useful context beyond those annotations, especially the distinction between scheduled and delivered, and explicitly states that no messages are sent or cancelled.

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 short, front-loaded with the main purpose, and each sentence adds a distinct piece of information: what is listed, how scheduled messages should be interpreted, and the read-only guarantee. No unnecessary filler.

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 the output schema is present and annotations are rich, the description is largely complete for a simple read-only listing tool. The main missing piece is explanation of pagination parameters, but defaults and the output schema help fill that in.

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 for parameter meaning. It only hints that chat_id identifies a chat ('in one chat') and does not explain limit or cursor behavior, pagination, or how the scheduled_at time relates to filtering. This is a meaningful gap.

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 identifies the action ('List') and resource ('scheduled messages in one chat'), and it distinguishes this tool from sibling tools that handle history or search. The clarifying phrase 'Scheduled does not mean delivered' reinforces the specific scope.

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 clearly frames when to use the tool: when you need scheduled messages for a specific chat. It does not explicitly name alternatives or exclusion criteria, but the scheduling context is enough to guide selection away from history, search, and thread tools.

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