telegram_read

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

No annotations are available, and the description provides no behavioral details such as idempotency, polling behavior, or side effects, leaving the agent with no insight into the tool's operations.

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 short (4 words), which might seem concise but actually under-specifies the tool, lacking necessary detail for an agent to use it effectively.

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 tool has 3 parameters, no output schema, and no annotations, the description fails to provide essential context such as pagination, authentication, or expected return format, making it inadequate for correct 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?

With 0% schema description coverage and no explanation of parameters (bot_token, offset, limit) in the description, the agent gains no understanding of how to use or fill these parameters correctly.

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 action (Read) and resource (Telegram messages/updates), but does not differentiate from the sibling tool 'telegram_get_updates', which likely has a very similar purpose.

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 like telegram_get_updates or telegram_search. The description only implies the basic usage without context or exclusions.

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