telegram-get-updates

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

Beyond annotations (readOnlyHint, openWorldHint), the description explains the return structure (newMessages, deletedMessageIds, otherUpdates, cursor), pagination behavior (isFinal flag), and stateless requirement for agent to persist cursor. 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?

The description is concise, front-loading key functionality, then covering returns, pagination, fallback, and statelessness. Every sentence is informative and avoids 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?

Despite no output schema, the description fully explains the return values (newMessages[], deletedMessageIds[], otherUpdates, cursor state) and the isFinal flag. It also covers the stateless cursor requirement and fallback behavior, making it complete for agent use.

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% with descriptions for each parameter. The description adds meaning by explaining the cursor concept, defaults for ptsLimit/ptsTotalLimit, and the condition for calling again (isFinal). However, the schema already handles most of the parameter semantics, so the added value is moderate.

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 'Fetch new messages, deleted messages, and other updates' with a cursor mechanism. It distinguishes from siblings like telegram-read-messages by mentioning a fallback hint, and references telegram-get-state for cursor initialization.

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?

Explicitly explains when to use (after obtaining a cursor), when to call again (isFinal=false), and provides fallback hint for resync via telegram-read-messages for gaps. This gives clear context for choosing this tool over alternatives.

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