discord_create_event_invite

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

Annotations already indicate the tool is not read-only (readOnlyHint=false) and not idempotent. The description adds that it requires a specific permission and returns the invite URL, which is useful beyond annotation. There is no contradiction; the description complements annotations well.

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 extremely concise with only two sentences, no fluff. The first sentence clearly states the action and result, and the second covers permission and return. Every sentence earns its place.

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 the comprehensive schema and annotations, the description is sufficient for an agent to use the tool correctly. It covers the core purpose, required permission, and return value. It could mention edge cases like external events requiring a channel_id, but that is in the schema. Overall, it is complete for the task.

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?

The input schema covers 100% of parameters with detailed descriptions. The tool description does not add parameter-specific meaning beyond the schema, which is acceptable given the high schema coverage. The description mentions 'shareable invite URL' as the outcome, but no additional parameter details.

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 a shareable invite URL for a scheduled event, using specific verbs and resources. It distinguishes itself from siblings like discord_create_invite by specifying that the invite points to an event, ensuring the agent understands the unique 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 explicitly mentions the required 'Create Instant Invite' permission, guiding when the tool can be used. However, it does not explicitly list alternatives or conditions when not to use it, though the purpose is distinct enough among siblings. A clear usage context is provided.

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