telegram-create-invite-link

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

Description only states 'create', which aligns with readOnlyHint=false (write operation). However, it does not disclose any additional behavioral traits, such as the need for admin rights, rate limits, or whether the link is automatically active. The openWorldHint=true annotation suggests possible side effects, but these are not explained.

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?

Single sentence of 10 words, front-loaded and efficient. No wasted words, but could be slightly longer to include essential guidance 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?

For a creation tool with 5 parameters and no output schema, the description is too minimal. It omits what the tool returns (the invite link), prerequisites (e.g., must be admin), and how it interacts with related tools. Siblings indicate a rich domain, but this description does not provide sufficient context for correct use.

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 coverage is 100%, and each parameter already has a clear description. The tool description adds no additional meaning beyond what is in the schema, so baseline score of 3 is appropriate.

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?

Clear verb and resource: 'Create a new invite link for a group or channel'. However, it does not distinguish from sibling like 'telegram-create-business-chat-link', which is a similar operation for business chats.

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 on when to use this tool vs alternatives. Siblings include 'telegram-revoke-invite-link', 'telegram-edit-business-chat-link', and 'telegram-get-invite-links', but the description provides no context for choosing this tool.

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