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

Annotations already declare this is a non-read-only, non-idempotent, non-destructive, open-world operation. The description adds only that the caller must be an owner or admin, and does not explain what the invite link represents, how it is constrained by parameters like days/uses/role, or what the caller should expect from the mutation.

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?

It is short, but it is a fragmented note rather than a front-loaded sentence. The brevity reflects under-specification, not efficient communication.

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 invite-creation mutation with no output schema and no schema descriptions, the definition is far too sparse. It states the permission level and URL pattern but omits the operational semantics an agent needs to call it 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 0% across five parameters. The description mentions only the invite URL form and does not explain group, days, from, role, or uses. This leaves every parameter undocumented both in the schema and the description.

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 reads as a sentence fragment ('Owner or admin: an invite link (https://...') rather than a clear statement of what the tool does. The tool name suggests creating an invite, but the description never explicitly says 'creates an invite link' or explains the effect of calling it.

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 states 'Owner or admin', which implies a permission prerequisite, but gives no guidance on when to use this instead of sibling tools such as group_invite_info, group_invite_revoke, or group_create. There are no alternatives or exclusion conditions mentioned.

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