discord_set_member_permission

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

The description discloses that the operation 'Merges with the member's existing overwrite' and requires 'Manage Roles permission'. These details go beyond the annotations, which only provide hints (idempotent, non-destructive). The agent gets clear behavioral expectations.

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?

The description is concise with four sentences, each carrying essential information: main action, behavioral detail (merge), prerequisite, and alternative tool. No unnecessary words or redundancy.

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, usage, permission requirements, and merge behavior. It does not explain potential error conditions or return values, but given no output schema and high schema coverage, this is not a critical gap. A score of 4 reflects minor missing context.

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 description coverage is 100%, so the schema already documents all parameters. The tool description does not add additional parameter-level detail beyond the schema's descriptions. A score of 3 is appropriate as the description does not need to compensate.

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 'Add or update a per-channel permission overwrite for a single member', with a specific verb and resource. It explicitly distinguishes from the sibling tool 'discord_set_role_permission', leaving no ambiguity.

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 explicit usage guidance: it requires 'Manage Roles' permission and directs to use 'discord_set_role_permission' for role-level changes. This clearly states when to use this tool and when to use an alternative.

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