discord_create_invite

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

Discloses that the tool creates a resource (invite link) with side effects (anyone with link can join), requires specific permissions, and returns the URL and code. Annotations indicate non-destructive, non-idempotent, open-world, which aligns with description. Adds value beyond annotations.

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?

Three sentences with zero wasted words. Front-loaded with core purpose, followed by security note, permission requirement, and return value. Highly efficient and well-structured.

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?

Given no output schema, the description correctly mentions return values (URL and code). Covers creation, constraints, permissions, and security. Minor gap: does not mention that the invite is tied to a specific channel (implied by purpose). Satisfactory for a 5-parameter 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?

Description only mentions limiting lifetime, uses, and membership type generically. All 5 parameters are fully described in the schema with 100% coverage. The description adds no new semantic information beyond what the schema already provides, so baseline score of 3 applies.

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?

Clearly states the action (create), resource (invite link for a channel), and optional constraints (lifetime, uses, membership type). Distinguishes from siblings like discord_create_event_invite and discord_list_invites.

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?

Explicitly mentions required permission (Create Instant Invite) and a security warning about the link granting server access. Provides clear context for when to use, though doesn't list alternative tools for different invite types.

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