Telegram MCP Server & Channel Monitor

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

Annotations already indicate this is not read-only (readOnlyHint: false) and not destructive (destructiveHint: false). The description adds that it sends messages and mentions Markdown support, which provides useful context beyond annotations. However, it doesn't disclose important behavioral aspects like rate limits, authentication requirements, or what happens with invalid chat IDs.

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 well-structured with clear sections (Args, Returns) and uses bullet points for parameters. It's appropriately sized at 4 sentences total. The first sentence clearly states the purpose, though the parameter explanations could be slightly more concise.

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 message-sending tool with 3 parameters and no schema descriptions, the description adequately covers the basics. It mentions the tool has an output schema (Returns section), so it doesn't need to detail return values. However, it lacks important context about error conditions, rate limits, and differentiation from sibling sending tools.

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 description lists all three parameters (chat_id, text, parse_mode) with brief explanations that mostly mirror the schema descriptions. With 0% schema description coverage, the description compensates by documenting the parameters, but doesn't add significant semantic value beyond what's already implied by parameter names. The mention of Markdown support for the text parameter is helpful context.

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 tool's purpose: '텔레그램 채팅에 메시지를 전송합니다' (sends a message to a Telegram chat). It specifies the verb ('전송합니다' - send) and resource ('텔레그램 채팅' - Telegram chat). However, it doesn't explicitly differentiate from sibling tools like 'telegram_send_with_buttons' or 'telegram_send_photo' that also send messages but with different capabilities.

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 alternatives. With many sibling tools for sending different types of content (photos, videos, documents, messages with buttons, etc.), there's no indication that this is specifically for plain text messages with optional Markdown/HTML formatting versus those other options.

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