discord_set_member_permission

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

Discloses the merge behavior ("Merges with the member's existing overwrite"), which is critical for understanding how the tool works. Annotations already indicate idempotent and non-destructive nature, so the description adds meaningful context. No contradiction with annotations.

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?

Concise three-sentence description with no fluff. First sentence states purpose, second adds behavioral detail, third covers prerequisites and alternatives. Well-structured 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?

Covers purpose, behavior, permissions, and differentiation from a sibling. Lacks explicit mention of return value, but given no output schema, this is acceptable. Overall informative for an agent to invoke 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?

All parameters have schema descriptions (100% coverage). The tool description adds context about the purpose of allow/deny arrays and the merge behavior, which aids interpretation beyond the schema alone.

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 the action (add/update), resource (per-channel permission overwrite for a single member), and effect (allow/deny). It distinguishes from discord_set_role_permission by directing to that tool for role-level changes.

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?

Explicitly states the required permission (Manage Roles) and directs to an alternative tool for roles. Could further clarify scenarios where this tool is inappropriate, but the guidance is clear enough.

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