Telegram MCP Server & Channel Monitor

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

Annotations already provide readOnlyHint=true and destructiveHint=false, indicating this is a safe read operation. The description adds valuable context by specifying the return format ('봇 정보 JSON 또는 에러' - bot info JSON or error), which helps the agent understand what to expect beyond just the safety profile. No contradictions with annotations exist.

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 perfectly concise with two sentences that each earn their place: the first states the purpose with examples, and the second clarifies the return format. No wasted words, and the information is front-loaded with the core functionality.

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 this is a simple read-only tool with 0 parameters, 100% schema coverage, annotations covering safety, and an output schema (implied by 'Has output schema: true'), the description provides exactly what's needed. It explains what the tool does and what it returns, making it complete for this level of complexity.

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 parameters and 100% schema description coverage, the baseline would be 4. The description appropriately doesn't discuss parameters since none exist, and instead focuses on the tool's purpose and return value, which adds meaningful context beyond the empty schema.

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 ('조회합니다' - retrieve/query) and resource ('현재 봇의 기본 정보' - current bot's basic information), with examples of what information is included (이름, username, id 등). It distinguishes itself from sibling tools that perform actions like sending messages, banning users, or editing content by focusing on bot metadata retrieval.

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 this tool should be used when needing bot information (name, username, ID), but doesn't explicitly state when to use it versus alternatives or provide context about prerequisites. No guidance is given about when NOT to use this tool or what other tools might serve similar purposes.

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