telegram_chat_get

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

With no annotations provided, the description carries the behavioral burden. It usefully states that the operation is read only and that it returns normalized details and permissions, but it does not explain access requirements, invalid chat_id behavior, rate limits, or what 'normalized' and 'permissions' concretely mean.

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 short sentences with zero waste. The main purpose is front-loaded and the read-only safety note is appended efficiently.

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?

For a simple single-chat read tool this is minimally adequate: it says what is retrieved and that it is read only. However, with no output schema or annotations, the return shape remains vague and the description does not explain how an agent should obtain or format chat_id.

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?

There is one required parameter, chat_id, with 0% schema description coverage. The description only repeats that the chat is identified by chat_id and does not explain the accepted format, such as numeric ID versus username, how to obtain it, or the schema's length constraints.

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 states a specific verb and resource: retrieves details and permissions for a specific chat. It clearly scopes the operation to one chat via chat_id, though it does not explicitly distinguish itself from siblings such as telegram_chats_list or telegram_messages_get.

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?

Usage is only implied by the mention of a specific chat and chat_id. There is no explicit guidance on when to use this instead of telegram_chats_list, nor any prerequisites, exclusions, or error conditions.

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