telegram_get_chat

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

The readOnlyHint annotation already covers the safety profile, and the description adds a useful behavioral nuance: for private chats it may return the other person's user_id and profile fields, but only when Telegram makes them available. It does not describe group/channel return details or error behavior, but these are minor gaps.

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?

Two sentences with no filler and the primary action is front-loaded. The private-chat caveat is meaningful and earns its place.

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 one-parameter read-only lookup with no output schema, the description covers the essential invocation requirements and one important return variance. It omits group/channel return specifics and not-found behavior, but these are secondary to correct selection and invocation.

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 defines chat_id as a required integer with no description (0% coverage). The description adds the key 'exact' matching semantics and clarifies this is a single-chat lookup, but it does not explain how to obtain the chat_id or any Telegram-specific ID conventions.

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 action (get details), a specific resource (one Telegram chat), and a hard lookup condition (exact chat_id). This clearly distinguishes it from sibling tools like telegram_list_chats, telegram_search_chats, and telegram_resolve_chat.

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 phrase 'by its exact chat_id' clearly implies the tool should be used when the caller already has the precise numeric identifier. It does not explicitly name alternatives or say when not to use it, but the context is clear enough.

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