discord_create_event_invite

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

Annotations already declare this is a non-readOnly, non-destructive, non-idempotent, open-world write. The description adds real value beyond that: the required permission, the fact that a URL is returned, and event-type-specific behavior where channel_id is required for EXTERNAL events and rejects for VOICE/STAGE_INSTANCE. It doesn't cover failure modes or what the invite object contains, keeping it short of a 5.

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?

Five short sentences, front-loaded with the core action, then permission, return value, the channel_id edge case, and the sibling pointer. No filler or redundant restatement of the name.

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?

There is no output schema, and the description compensates by stating it returns the invite URL. With annotations covering safety signals and 100% parameter documentation, the definition covers everything an agent needs to select and invoke this write tool 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 100%, and the schema already spells out max_age, max_uses, event_id, guild_id and the EXTERNAL/VOICE/STAGE_INSTANCE rule for channel_id. The description restates the channel_id branching but adds no additional meaning beyond what the schema documents, so the baseline 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?

Description states a specific verb and resource (create a shareable invite URL) and a specific scope (linked to a scheduled event, so recipients land on the event). It explicitly distinguishes itself from the sibling discord_create_invite, so an agent can pick correctly without opening schemas.

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?

Gives an explicit alternative and the condition that selects it: plain channel invite with no event attached goes to discord_create_invite. It also states the prerequisites (Create Instant Invite permission) and the branch condition for channel_id (required for EXTERNAL events, rejected for others), which is exactly the decision the agent needs to make before calling.

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