Update Discord scheduled event

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

Annotations already declare destructiveHint=true and idempotentHint=true, so the safety profile is covered structurally. However, the description adds nothing on behaviors an agent needs: the presence of a 'confirm' parameter implies a confirmation step that is never explained, and there is no hint about which Discord permissions are required or whether omitted fields are preserved or cleared.

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 single sentence is short but fails the conciseness test by under-specification rather than efficiency — it is a redundant echo of the title with no front-loaded detail about scope, required IDs, or mutation semantics.

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 15-parameter destructive mutation with a nested object and only 2 required fields, the description is completely inadequate. Even with annotations and an output schema covering some ground, an agent has no basis for choosing values for the many optional fields or understanding the confirm workflow.

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?

With 15 parameters, 0% schema description coverage, and a nested entityMetadata object, the description contributes no parameter meaning at all. Cryptic fields such as entityType, privacyLevel, status, and confirm (which accept string-or-number unions with no enums declared) are left entirely unexplained.

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 restates the tool name and title verbatim ("Update a Discord scheduled event") without adding scope, affected fields, or any differentiation from siblings like discord_create_scheduled_event or discord_delete_scheduled_event. The verb+resource is present but conveys no more than the identifier already does.

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?

There is no guidance on when to use this tool versus the create/delete/list scheduled-event siblings, no mention of prerequisites such as the event needing to exist or the guildId/eventId being required, and no note about what state the event must be in to accept updates.

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