Group invite link

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly warns about the destructive revoke action ('revoke the old one') and states the admin requirement. However, it does not mention behavior like whether a link is created if none exists, or the exact response format, so it is not fully 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 two concise sentences with no redundant phrasing. It front-loads the primary purpose, then states the optional revoke behavior and the admin requirement. Every sentence adds meaningful 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 two-parameter tool with no output schema, the description covers the core operation, the optional destructive mode, and a key prerequisite (admin). It does not explicitly state what the tool returns, but 'Get the join link' strongly implies the output. Minor gaps remain, such as behavior when no link exists, but the description is adequate for a low-complexity tool.

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 parameters 'group' and 'revoke' are already well documented in the schema. The description adds no additional parameter-level meaning beyond what the schema provides. The baseline of 3 applies because the schema carries the parameter documentation burden.

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 the specific action: 'Get the join link for a group, or revoke the old one and issue a fresh link.' This distinguishes the tool from all siblings by focusing on the invite link resource, which no other sibling explicitly offers. The optional revoke behavior is also clearly identified.

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 a clear context for the tool's operation, especially the 'Requires admin' prerequisite, but it does not explain when to use this tool versus alternatives. No sibling is mentioned, and there is no explicit when-not-to-use guidance. The usage context is implied rather than fully articulated.

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