discord_lock_channel_permissions

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

Annotations already mark it as non-read-only and idempotent; the description adds that existing overwrites are reset to match the parent, that a category is required, and that a confirmation is returned. It could more explicitly warn that channel-specific overrides are discarded, but 'exactly match' conveys the effect.

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 sentences, each earning its place: the core operation, the prerequisite, and the permission/return behavior. Information is front-loaded and there is no filler.

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 one-parameter mutation with no output schema, the description covers what happens, the precondition, the required permission, and the return behavior. Combined with the annotations (idempotent, non-destructive, non-read-only), nothing essential is missing for correct invocation.

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?

The single parameter has 100% schema description coverage, so the schema already documents channel_id as a snowflake of the channel to sync. The description reinforces the category requirement but adds no new parameter-level detail beyond the schema.

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 leads with a specific action and resource: 'Reset a channel's permission overwrites to exactly match its parent category.' The parenthetical '(Discord's sync permissions)' anchors the behavior in Discord terminology, making it clearly distinguishable from generic permission tools even though no sibling is named.

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?

It gives clear eligibility and permission context: the channel must be inside a category and the caller needs Manage Roles. It does not explicitly name alternatives like discord_reset_channel_permissions or state when not to use this tool, but the context is sufficient for correct selection.

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