discord_lock_channel_permissions

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

Annotations already provide idempotentHint=true, destructiveHint=false, and readOnlyHint=false. The description adds that the operation resets permissions, returns a confirmation, and requires Manage Roles. No contradiction with annotations; it enriches the behavioral context beyond what annotations offer.

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?

Two sentences: first states the action with a parenthetical, second adds constraints and result. Every sentence earns its place; no wasted words. Efficient and front-loaded.

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?

Given a simple single-parameter tool with no output schema, the description covers the action, prerequisites, permission requirement, and return value. It is self-contained and sufficient for an agent to use correctly.

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 channel_id has 100% schema coverage with a description. The tool description adds 'ID (snowflake) of the channel to sync with its parent category', clarifying its role in the sync operation. This adds meaning beyond the schema, which already describes the ID.

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 'Reset a channel's permission overwrites to exactly match its parent category', specifying a specific verb (reset/sync) and resource (channel permissions). It distinguishes from siblings like discord_reset_channel_permissions and discord_copy_permissions by the sync behavior, but does not explicitly name alternatives. Clear but lacks explicit sibling differentiation.

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 for use: 'The channel must be inside a category. Requires the Manage Roles permission.' It implies when to use (sync permissions) but does not explicitly state when not to use or suggest alternative tools. Adequate but no exclusionary guidance.

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