telegram_get_chat

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

No annotations are provided, so the description must carry the full behavioral burden. It mentions the return format, but does not disclose authorization requirements, possible errors, rate limits, or that the bot may need to be a member of the chat. The read-only nature is only implied by the verb 'Get'.

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 concise and front-loaded: the main purpose is stated first, followed by a compact return summary and parameter documentation. No filler or redundant sentences are present.

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?

The tool is simple, has one parameter, and an output schema exists, so the description is mostly adequate. However, it omits sibling-tool selection guidance, the practical requirement that chat_id must actually be provided despite the schema default, and behavioral details such as permissions and error conditions.

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?

Schema description coverage is 0%, and the description compensates by explaining chat_id as a 'Unique identifier for target chat or @channelusername'. This adds meaningful format guidance beyond the bare schema, though it does not clarify why chat_id is optional in the schema or what happens if it is null.

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 verb and resource: 'Get detailed information about a chat', and enumerates chat types and returned fields. It is distinguishable from send/delete siblings, but it does not explicitly differentiate from the sibling getter tools like telegram_get_chat_member_count or telegram_get_chat_administrators.

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 no guidance on when to use this tool versus the sibling getters. There is no mention of when to choose get_chat over get_chat_member_count or get_chat_administrators, nor any exclusions or prerequisites.

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