read_messages

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

No annotations are provided, so the description must disclose behavioral traits like idempotency, rate limits, or authentication needs. The description only states the basic operation (read messages) and does not mention if the tool is read-only, what happens on invalid chat IDs, or if pagination behavior (offset_id) has any side effects.

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 two sentences long, concise and front-loaded with the core purpose. It avoids fluff but could combine the sentence about chat source into the first sentence for even tighter prose.

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 no output schema, the description does not need to detail return fields. The parameter set is fully covered in schema. However, with no annotations, the description lacks behavioral context (e.g., is this a safe read operation?). Completeness is adequate for a simple read tool but not thorough.

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 schema has 100% description coverage, so parameters chat, limit, search, and offset_id are already documented with types, defaults, and descriptions. The description adds minimal value beyond restating that chat can be an ID or @username. With full schema coverage, baseline is 3.

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 precisely states that the tool reads messages from a Telegram chat, channel, or group, specifying the source as a chat ID or @username. This clearly distinguishes it from sibling tools like send_message (write) and get_chat_info (metadata), and aligns with list_chats as a prerequisite.

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 hints at usage by mentioning chat ID from list_chats, implying that one should first use list_chats to get the ID. However, it does not explicitly state when to use this over search_messages (which searches across chats) or how to handle channels vs. groups. No exclusions or alternatives are given.

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