discord_edit_scheduled_event

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

Adds real context beyond annotations: partial-update semantics (consistent with idempotentHint=true), the permission gate, and status-transition constraints. It does not describe the response or what happens to event subscribers when an event is canceled, keeping 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 compact sentences, front-loaded with the patch semantics, followed by status behavior and the permission requirement. No filler and every sentence carries information the agent needs.

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 10-parameter mutation tool with annotations covering safety and idempotency and a fully documented schema, the description covers partial update, status transitions, and permissions. Return value and post-cancellation effects are omitted, which is acceptable given no output schema expectation but leaves a small gap.

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% and each parameter already documents format and constraints, including the status enum's allowed transitions. The description restates the status behavior rather than adding new parameter-level meaning, so the baseline 3 applies.

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?

States a specific verb and resource ('Update a scheduled event') plus the patch semantics ('only provided fields change'), which distinguishes it from discord_create_scheduled_event and discord_delete_scheduled_event in the sibling set. It does not explicitly name those siblings, so it stops short of a 5.

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?

Explains when to use the status field (start/end/cancel), warns that Discord only permits certain transitions, and states the Manage Events permission prerequisite. It does not explicitly route the agent away from create/delete siblings, but the usage context is unambiguous.

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