discord_edit_channel

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=true, so safety and idempotency are covered. The description adds the permission requirement and the partial-update behavior, which is genuinely useful context. It stops short of describing rate limits or side effects of archiving.

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 short lines: action list, partial-update caveat plus permission, and return summary. Front-loaded with the operations and no wasted clauses.

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?

Output schema exists, so return values needn't be explained; the description still summarizes the confirmation. Permissions and partial-update semantics are covered. Minor gap: no mention of thread-vs-channel field restrictions beyond the per-param notes in the 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?

Schema description coverage is 70%, with several params (locked, reason, archived, position, parent_id, slowmode_seconds) already documented in the schema. The description's list of actions maps to those params but adds no format or unit detail beyond the schema. Baseline 3 is appropriate.

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?

Specific verb list (rename, retopic, move, slowmode, archive/lock) plus the resource (channel/thread). It clearly distinguishes itself from siblings like discord_create_channel or discord_delete_channel by being the edit tool.

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?

States 'Only the fields you pass are changed' and the required permission (Manage Channels / Manage Threads for threads), which tells the agent when the call will succeed. It does not name sibling alternatives, but the edit-vs-create/delete distinction is implied by the verb set.

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