telegram_get_updates

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

Annotations indicate readOnlyHint=true and idempotentHint=true. The description adds context by explaining that updates are marked as read and paginated via offset, which is a behavioral trait beyond the annotations. No contradiction, and the description enhances understanding of the tool's idempotent behavior.

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: four sentences plus essential Args/Returns sections. It front-loads the purpose and immediately follows with key usage guidance. No filler or redundant information.

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 complexity of a polling tool, the description covers the core mechanism (offset pagination) and filtering. It mentions the return format (JSON). With annotations providing safety cues and the presence of an output schema, the description is largely complete, though it could mention the default limit or rate limits (but not critical).

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?

The description adds meaning beyond the input schema by explaining how to use the 'offset' parameter for pagination and acknowledgment. Although the schema has descriptions (e.g., for offset), the tool description provides a usage pattern (last_update_id + 1) that is not in the schema. The 'allowed_updates' filter is mentioned briefly but not elaborated.

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 'Retrieve recent updates', specifying the verb (retrieve) and resource (updates). It differentiates from sibling tools like telegram_send_message or telegram_delete_message, which perform different actions.

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 provides explicit guidance on using the 'offset' parameter for pagination and acknowledgment: 'Call with offset = (last_update_id + 1) to acknowledge processed messages.' It also mentions the 'allowed_updates' filter. However, it does not explicitly state when not to use this tool or compare with alternatives like telegram_get_chat_info.

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