discord_lock_channel_permissions

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

Annotations indicate readOnlyHint=false, destructiveHint=false, idempotentHint=true. The description adds context beyond annotations: specifies the exact behavior (reset to match parent), the prerequisite (channel must be in category), required permission, and return value (confirmation). No contradiction.

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: action, prerequisite, outcome. No filler, front-loaded with the primary purpose. Each sentence adds essential information with zero waste.

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 simple one-parameter tool with no output schema, the description explains the action, prerequisites, and return value. It does not detail error cases or confirmation format, but is sufficient for correct invocation given the annotations and 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 coverage is 100% and describes channel_id sufficiently. The description adds no extra parameter details beyond the schema, but the tool-level context (channel must be in category) reinforces the parameter's role. 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 uses specific verb 'reset' and resource 'permission overwrites', explicitly stating the action: sync to parent category. It distinguishes from siblings like discord_reset_channel_permissions by mentioning 'Discord's sync permissions' and the parent category requirement.

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 clearly states prerequisites: channel must be in a category and requires Manage Roles permission. It does not explicitly compare with alternatives like discord_copy_permissions or discord_reset_channel_permissions, but the context is clear enough for an agent.

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