telegram_get_messages

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

With no annotations, description correctly identifies read operation but does not explicitly state absence of side effects or rate limits, leaving behavioral traits partially uncovered.

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?

Single sentence is front-loaded with purpose and parameter clarification, containing no unnecessary words.

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?

Description covers basic purpose and chat format, but lacks details about return structure or pagination; absence of output schema increases need for such info.

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?

Description clarifies chat parameter format beyond schema, but does not address limit or search parameters; schema coverage is 67%, so description only partially compensates.

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?

Description specifies verb 'Read' and resource 'messages' from a Telegram chat, clearly distinguishing from sibling tools like telegram_get_dialogs and telegram_send_message.

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?

Description implies usage for reading messages but lacks explicit guidance on when to use vs alternatives, though tool name makes it straightforward.

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