Create an additional Telegram invite link for a chat, optionally setting an expiry date, member limit, join-request approval, or a custom name.
Create an additional invite link.
| Name | Required | Description | Default |
|---|---|---|---|
| name | No | ||
| chat_id | Yes | Chat ID or @username | |
| expire_date | No | ||
| member_limit | No | ||
| creates_join_request | No |
Changes observed during successful MCP inspections.
v0.2.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate this is a non-read-only, non-idempotent, non-destructive operation. The description adds no extra behavior context (e.g., that existing invite links remain valid, or that each call creates a fresh link). No contradiction exists, but the description fails to add value beyond the structured hints.
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 concise sentence, front-loaded with the verb, but it is under-specified rather than efficiently informative. It lacks essential context, so it is not a model of concise clarity—brevity at the expense of meaning.
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 tool with five parameters, no output schema, and a rich set of related invite-link tools, this description is far too sparse. It does not clarify what the return value represents (the invite link object), how parameters interact, or the tool's relationship to other invite link functions, leaving significant gaps in an agent's understanding.
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 only 20%, with four parameters (name, expire_date, member_limit, creates_join_request) completely undocumented. The description does not explain any parameter meaning or how they affect the invite link, making it difficult for an agent to choose correct values.
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 verb 'Create' and resource 'additional invite link' clearly state the action. The word 'additional' distinguishes this from export_chat_invite_link (primary link) and create_chat_subscription_invite_link (subscription-based). However, it doesn't explicitly mention the chat context, relying on the tool name and sibling list for full clarity.
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?
No guidance is provided on when to use this tool versus alternatives like export_chat_invite_link, edit_chat_invite_link, or revoke_chat_invite_link. Prerequisites such as bot admin rights or chat permissions are not mentioned, leaving the agent without decision support.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.