export_chat_invite_link

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

The description explicitly discloses the destructive effect by stating 'revokes previous one', which directly aligns with the annotations destructiveHint=true and readOnlyHint=false. It adds specific context about what gets destroyed beyond the generic annotation flags.

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 containing only necessary information: 'Generate a new primary invite link (revokes previous one).' It is front-loaded, concise, and free of unnecessary words.

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 one-parameter tool with no output schema, the description covers the core behavior and its destructive side effect. It does not explicitly state the return value (presumably the new invite link), but this is a minor gap given the tool's low complexity and the fact that the only parameter is already fully documented.

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?

The input schema fully documents the only parameter 'chat_id' with description 'Chat ID or @username', achieving 100% schema coverage. The tool description adds no additional parameter semantics, so the 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?

The description uses the specific verb 'Generate' with the resource 'primary invite link', and explicitly states the side effect 'revokes previous one'. This distinguishes it from sibling tools like create_chat_invite_link (secondary links) and revoke_chat_invite_link (revoking arbitrary links).

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 clear context that this is for generating the primary invite link, implying it's the go-to for primary link replacement. However, it does not explicitly mention when to use this instead of create_chat_invite_link or revoke_chat_invite_link, so no explicit exclusion is given.

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