createChatInviteLink

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

With no annotations, the description carries the full burden of behavioral disclosure. It covers the authorization requirement, the fact that the link is revocable, and the return type. It does not mention rate limits or specific failure modes, but the core behavioral profile is transparent.

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 three short sentences, each contributing a distinct fact: what the tool creates, required permissions, revocability, and return type. There is no filler or redundancy.

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 five-parameter mutation tool with no annotations and no output schema, the description covers the essential context: purpose, permission requirement, lifecycle, and return type. It leaves some sibling differentiation implicit, but the schema handles parameter constraints and the description is otherwise complete enough to invoke 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?

The input schema covers all five parameters with descriptions, giving 100% schema coverage, so the baseline is 3. The description does not add parameter-level meaning beyond what the schema already provides, but it also does not need to compensate for any schema gaps.

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 states a specific action and resource: 'Create an additional invite link for a chat.' The word 'additional' helps distinguish this from exporting the primary invite link, but it does not explicitly differentiate it from sibling methods like createChatSubscriptionInviteLink or editChatInviteLink.

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 gives clear usage context by specifying that the bot must be an administrator with can_invite_users rights, and it notes that the link can later be revoked via revokeChatInviteLink. However, it does not explicitly state when to prefer this tool over related invite-link alternatives, so it stops short of full alternative routing.

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