discord_set_role_permission

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

Discloses merge behavior ('Merges with the role's existing overwrite'), which adds context beyond annotations. Annotations indicate idempotentHint=true and destructiveHint=false, consistent with description. No contradictions.

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 efficiently cover purpose, behavior, permission requirement, and alternative tool. No wasted words.

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 mutation tool without output schema, the description sufficiently explains action, merge semantics, required permission, and differentiation from sibling tool. No gaps.

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?

All 5 parameters have complete descriptions in the input schema (100% coverage). The description adds no additional parameter-level details beyond what the schema already provides, so baseline 3 applies.

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?

Description explicitly states 'Add or update a per-channel permission overwrite for a role, allowing and/or denying specific permissions.' It identifies the specific verb (add/update), resource (permission overwrite for a role), and distinguishes from sibling tool discord_set_member_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?

Description provides clear context: requires 'Manage Roles' permission, specifies merge behavior (does not reset), and directs to an alternative tool (discord_set_member_permission) for targeting a single member.

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