discord_create_invite

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

The description adds behavioral context beyond annotations: it warns that anyone with the link can join the server, which is a critical side effect, and specifies the required permission. Annotations already indicate non-readonly and non-destructive, but the description enriches the safety profile.

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: the first states purpose and optional behavior, the second covers security, permission, and return value. It is front-loaded and contains no superfluous text.

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?

Despite lacking an output schema, the description notes the return (URL and code) and covers the main behavioral options. It does not detail error scenarios, but for a creation tool with clear parameters, it is largely complete.

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?

All parameters have descriptions in the schema (100% coverage), so the description's mention of 'lifetime, uses, and membership type' only summarizes without adding new details. The baseline of 3 is appropriate since schema already carries full documentation.

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 tool creates an invite link for a channel, with optional lifetime, uses, and membership limits. It distinguishes itself from sibling tools like discord_create_event_invite and discord_delete_invite by focusing on channel invites and using specific verbs.

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 some guidance by noting the security implication and required permission. However, it does not explicitly say when to use this tool versus alternatives like discord_create_event_invite or when not to use it, leaving the agent to infer from context.

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