Update Discord channel

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

Annotations already flag destructiveHint=true and idempotentHint=true, so the safety profile is partly covered. But the description says nothing about the destructive implications, the existence of the 'confirm' gate, the audit-log 'reason' field, or whether omitted fields are left untouched — all of which matter for a mutation tool.

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?

A single front-loaded sentence with no padding, which is structurally clean. The problem is under-specification rather than verbosity — the space saved is not spent on anything an 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?

The output schema exists, so return values need not be explained. But for an 11-parameter, destructive, open-world mutation with zero schema coverage, an agent cannot determine the confirm/reason conventions or channel-type constraints from this description alone.

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 0% across 11 parameters, so the description carries the full burden and largely fails. It names only 3 of 11 parameters with no added semantics (no units for bitrate, no note that userLimit 0 means unlimited), and omits confirm, reason, parentId, topic, nsfw, name and rateLimitPerUser entirely.

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 verb+resource is clear (update a guild channel) and it is distinguishable from create/delete/reorder siblings. However, the enumerated properties (bitrate, user limit, RTC region) are only the voice-channel ones, which misrepresents the scope of a tool that also edits name, topic, nsfw, parentId and rateLimitPerUser, and steers agents away from legitimate text-channel updates.

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?

No guidance on when to use this versus discord_set_channel_permissions, discord_reorder_channels, or discord_set_voice_channel_status, all of which overlap on channel state. Nothing is said about required permissions (Manage Channels) or which channel types accept which fields.

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