get_chat_info

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states it gets information but does not clarify the nature of the operation (e.g., read-only vs. potentially heavy), authentication needs, error behaviors, or what 'detailed information' includes. The description lacks sufficient behavioral context.

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 a single sentence that directly states the purpose. It is concise and front-loaded, with no wasted words. However, it could benefit from a minor structural addition (e.g., a second sentence about typical use) without losing conciseness.

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 has only one parameter with good schema coverage, but lacks an output schema and annotations. The description does not elaborate on what 'detailed information' includes or how to interpret the output. While adequate for a simple read tool, it leaves room for ambiguity about the response format or potential limitations.

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 100%, so the schema already documents the single parameter 'chat' as accepting a numeric ID or @username. The description does not add extra meaning beyond what the schema states, returning to baseline of 3. No value added.

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 'Get' and the resource 'detailed information about a Telegram chat, channel, or group', which distinguishes it from sibling tools like 'list_chats' (listing) or 'send_message' (sending). The scope is specific and unambiguous.

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 does not provide any guidance on when to use this tool versus the listed sibling tools. No context is given about usage scenarios, prerequisites (e.g., needing the chat ID), or when alternatives would be more appropriate.

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