Create event

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

Annotations already indicate readOnlyHint=false, which is consistent with 'Create'. The description adds behavioral context: members see the event on the events list and can mark interest, and external events are 'in-person or off-platform.' It does not disclose permission requirements or return behavior, but with annotations present, this is sufficient.

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, no filler. The first sentence states purpose, the second disambiguates from siblings, and the third gives type-specific requirements.

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 purpose, type variants, sibling exclusions, and parameter relationships. It does not mention return values, but no output schema exists; overall it is complete for a creation tool with this schema.

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 description explains the conditional use of parameters: channel is required for voice/stage, while location and end_time are required for external events. It also clarifies the meaning of 'external' beyond the schema's enum. Schema coverage is 67%, and the description compensates for the remaining gaps.

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 uses the specific verb 'Create' and identifies the resource as 'Discord scheduled community event' with explicit variants (voice, stage, external). It also distinguishes from siblings by explicitly naming schedule_message and subscribe_events.

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?

It explicitly states what the tool is not for: 'This is not for sending a message later (use schedule_message) or watching live activity (use subscribe_events).' It also provides conditional requirements for event types (voice/stage need a channel; external needs location and end time).

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