discord_create_scheduled_event

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

Annotations already indicate this is a write operation (readOnlyHint=false) and not destructive (destructiveHint=false). The description adds the requirement for the 'Manage Events' permission and states that it returns the new event's name and ID. No contradictions with 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 that are front-loaded with the core purpose. Each sentence adds necessary information without redundancy. Very concise 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?

The description covers the main aspects: action, variant usage, permissions, and return value. Given the 9 parameters and no output schema, it provides sufficient information for an agent to decide whether and how to use the tool. Could mention when to use this vs creating a simple invite, but not essential.

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 coverage is 100%, so all parameters have descriptions in the schema. The description adds additional context by explaining which parameters are needed based on entity_type, which goes beyond the schema's property descriptions and provides meaningful guidance for correct invocation.

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 starts with 'Create a scheduled event', using a specific verb and resource. It distinguishes this tool from siblings like edit and delete by implying creation only. The differentiation between entity types is clear.

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 explicit instructions for when to use channel_id (for VOICE/STAGE_INSTANCE) and when to use location + scheduled_end_time (for EXTERNAL). It also mentions the required 'Manage Events' permission. However, it does not contrast with other creation tools like creating an invite or channel, but given the context, it's clear enough.

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