editChatSubscriptionInviteLink

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

With no annotations, the description carries the behavioral disclosure burden. It does disclose the permission requirement and that the return value is a ChatInviteLink object, which is helpful. However, it does not mention possible side effects of editing, failure modes, or idempotency for a mutation operation.

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 two concise sentences with no filler: purpose first, then prerequisite and return type. Every clause adds useful information.

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 simple three-parameter tool with fully described schema fields, the description supplies the key missing context: permission requirements and return type. A small gap is the lack of explicit contrast with editChatInviteLink, but the resource name and scope largely cover this.

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 100%, so the schema already documents all three parameters. The description adds no additional parameter-level meaning beyond noting the return object, so the baseline score of 3 applies.

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 a specific action ('Edit'), a specific resource ('subscription invite link'), and scopes it to links 'created by the bot.' The term 'subscription' distinguishes this from the sibling editChatInviteLink for ordinary invite links without needing to open the schema.

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?

It provides a useful prerequisite ('bot must have can_invite_users administrator rights') and narrows applicability to subscription invite links created by the bot. However, it does not explicitly contrast with alternatives like createChatSubscriptionInviteLink or editChatInviteLink, so the selection logic is mostly implied.

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