poll_telegram_updates

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

With no annotations, the description carries the full burden of behavioral disclosure. It only states the action (poll and forward) without revealing details like whether this is a continuous or one-shot poll, whether it requires an existing webhook, how errors are handled, or what happens to updates that are already forwarded. This is a minimal disclosure.

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 a single clear, front-loaded sentence with no wasted words. It efficiently conveys the primary action and output in a compact form.

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?

Even though this is a simple no-parameter tool (and an output schema exists), the description lacks essential context about the operational environment. It doesn't mention whether a webhook must already be set, how polling is triggered, or what happens to the updates after forwarding. Given the low complexity, this is still a notable gap for agents deciding when and how to invoke it.

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 input schema has zero parameters, so the baseline is 4 per guidelines. The description adds no parameter-specific meaning, but none is needed; it correctly implies the tool requires no inputs and does what it says.

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 a specific action ('Poll') on a specific resource ('Telegram') with a defined result ('forward them to local webhook'). It is immediately distinguishable from sibling tools like set_telegram_webhook and check_telegram_webhook, which manage webhook configuration rather than polling for updates.

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites (e.g., a configured webhook), nor does it exclude situations where polling is inappropriate. Given sibling tools for webhook management, this omission leaves the agent to infer usage context.

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