discord_create_scheduled_event

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

Annotations already declare this is a non-read-only, non-destructive, non-idempotent, open-world write. The description adds meaningful context beyond that: the Manage Events permission requirement and the shape of the return (new event's name and ID). It doesn't discuss duplicate-event behavior or what happens on permission failure, which keeps it below 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?

Three sentences, no filler: action, conditional requirements, permission + return shape. The most decision-relevant information is front-loaded.

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?

No output schema exists, and the description compensates by naming the return fields. It covers the entity-type branching, permissions, and result. Minor gaps: no note on optional image/description fields or rate limits, though the schema handles the former.

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 already documents every parameter, including the entity_type enum itself stating the same channel_id / location + scheduled_end_time conditions. The description restates that cross-field requirement in one place, which is mildly useful but largely duplicative of structured data.

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?

Opens with a specific verb+resource ('Create a scheduled event'), which cleanly separates it from the list/get/edit/delete scheduled-event siblings. It doesn't explicitly name those siblings, but the create semantics are unambiguous.

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 clear conditional guidance tied to entity_type: channel_id for VOICE/STAGE_INSTANCE, location + scheduled_end_time for EXTERNAL. No explicit 'use X instead' routing against siblings, so it stops short of a 5, but the context is actionable.

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