Telegram MCP Server & Channel Monitor

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the agent knows this is a safe read operation. The description adds useful context about what information is returned (chat name, type, member count, description), which goes beyond the annotations. However, it doesn't mention rate limits, authentication requirements, or error conditions.

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 appropriately sized with a clear purpose statement followed by Args and Returns sections. The structure is logical and front-loaded. The Korean text is efficient, though the English translation in the response format adds some redundancy.

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?

Given the simple single-parameter read operation with good annotations and an output schema (implied by 'Returns' section), the description is reasonably complete. It explains what information is returned, though doesn't detail the JSON structure. For this complexity level, it provides sufficient context for agent usage.

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?

With 0% schema description coverage (the schema has no parameter descriptions), the description fully compensates by clearly explaining the single parameter's purpose ('조회할 채팅 ID' - chat ID to retrieve). The description adds complete semantic meaning beyond the bare schema, though it doesn't specify format constraints (e.g., numeric ID vs username).

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 specific action ('조회합니다' - retrieves/looks up) and resource ('채팅/그룹/채널의 상세 정보' - detailed information of chat/group/channel), with explicit scope ('채팅 ID로' - by chat ID). It distinguishes from siblings like telegram_get_chat_members_count (which only gets member count) and telegram_get_me (which gets bot info).

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 implies usage when detailed chat information is needed, but doesn't explicitly state when to use this tool versus alternatives. It doesn't mention prerequisites (e.g., bot must be a member) or exclusions. The context is clear but lacks explicit guidance on tool selection.

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