edit_chat_subscription_invite_link

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

The annotations already declare readOnlyHint=false, destructiveHint=false, and idempotentHint=true, covering the safety profile. The description adds no further behavioral context, such as whether changes are reversible or what actually gets edited beyond the verb 'Edit'. It does not contradict the annotations, but it also does not enrich them.

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 sentence with no wasted words, making it concise, but it is under-specified. While the front-loaded structure is fine, the extreme brevity fails to convey essential usage or parameter context, so it is not appropriately sized for the tool's complexity.

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?

This is a write operation with no output schema and sparse parameter descriptions. The description does not explain what aspects of the subscription invite link can be edited, how it differs from regular invite link editing, or any side effects. Given the available annotations and schema, the description leaves significant gaps for the agent to operate correctly.

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 33% (only chat_id is described). The description names the resource but does not explain what 'name' or 'invite_link' parameters do in this context. With low schema coverage, the description should compensate, but it does not, leaving the semantics of two parameters entirely to inference.

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 uses a specific verb 'Edit' and a specific resource 'subscription invite link', which clearly distinguishes it from the sibling tool 'edit_chat_invite_link' that edits regular invite links. However, it is minimal and does not mention the chat context explicitly, though the resource name is fairly clear.

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 such as 'edit_chat_invite_link' or 'create_chat_subscription_invite_link'. There is no mention of prerequisites, exclusion criteria, or preferred scenarios, leaving the agent to infer usage from the name alone.

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