discord_create_event_invite

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

Annotations already indicate this is a non-read-only, non-destructive, non-idempotent action. The description adds useful context beyond that by disclosing the permission requirement ('Requires the Create Instant Invite permission') and stating the output ('Returns the invite URL'). It does not cover failure or rate-limit behaviors, but the added auth prerequisite is valuable.

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 sentences with no filler. The primary action and outcome are front-loaded, and the permission requirement and return value are stated without redundancy.

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 tool with well-documented parameters and no output schema, the description covers the key missing pieces: the permission needed, the invite's purpose, and the return value. The agent has enough to select and invoke this tool correctly without additional context from sibling descriptions.

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 schema fully documents all five parameters, including defaults, ranges, and special cases such as channel_id being required for external events. The description adds no additional parameter-level detail, which matches the baseline expectation of 3 for high schema coverage.

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 states a specific verb ('Create'), a specific resource ('shareable invite URL'), and a distinct target ('points to a scheduled event'). This clearly separates it from the sibling discord_create_invite, whose scope is a regular channel invite. The phrase 'so recipients land on the event when joining' further sharpens the purpose.

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 implies the use case by explaining that the invite points to a scheduled event and mentions the required 'Create Instant Invite' permission. However, it does not explicitly contrast this with discord_create_invite or state when a regular invite should be used instead, so usage guidance is inferred rather than explicit.

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