discord_reset_channel_permissions

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

The description discloses the destructive nature (irreversible, overwrites cleared) and the required permission, adding value beyond annotations. Annotations already had destructiveHint=true and idempotentHint=true, but the description reinforces and explains consequences.

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 terse sentences, each earning its place: purpose, warning, permission. Front-loaded with the main action.

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 description covers purpose, behavior, permission, and irreversibility. It lacks details on return value or confirmation, but for a destructive reset operation, the key aspects are well addressed.

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% with descriptions for both parameters (channel_id, reason). The description does not add extra meaning beyond the schema, so 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?

The description clearly states the tool removes all permission overwrites on a channel, resetting to defaults. It uses specific verbs and the resource, distinguishing it from sibling tools like copy_permissions or set_role_permission.

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 warns that the operation is irreversible and requires Manage Roles permission, giving clear context for when to use. It does not explicitly compare with alternatives, but the irreversibility hint is strong guidance.

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