discord_edit_channel

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

Annotations already indicate idempotent and non-destructive behavior. The description adds that the tool returns a confirmation and that only provided fields change. It does not detail side effects, rate limits, or audit log implications, but is consistent with annotations.

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: first defines purpose and fields, second adds constraints, third states return value. No unnecessary words, front-loaded with key information.

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?

Covers purpose, constraints, permissions, and response. Lacks explicit mention that NSFW flag applies to all channels or that name has a max length (covered by schema). Overall sufficient given schema and annotations.

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%. The description adds value by clarifying that slowmode also applies only to text channels (schema only mentions it for topic) and that the update is partial. This supplements the schema descriptions.

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 clearly states the verb 'Update' and specifies the resource 'channel', and lists specific fields (name, topic, slowmode, NSFW flag) that can be modified. This distinguishes it from sibling tools like discord_edit_message or discord_edit_role.

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?

The description provides context on partial updates ('Only provided fields change') and channel-type constraints ('topic and slowmode apply to text channels only'). It also mentions required permission. However, it does not explicitly contrast with alternative tools like discord_set_channel_position or discord_move_channel.

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