discord_add_role

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

Discloses required permissions, role hierarchy condition, and idempotent behavior. Annotations provide idempotentHint=true, and description adds valuable context beyond annotations, with 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?

Three sentences, each essential: purpose, permissions/constraint, idempotency and undo. No wasted words, front-loaded with key information.

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 all necessary information for correct usage: purpose, permissions, hierarchy, idempotency, and alternative tool. No output schema needed; description is complete for a simple idempotent mutation.

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?

Input schema has 100% description coverage for all parameters. The description does not add additional parameter-level information beyond what the schema provides, meeting the baseline of 3.

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?

Clearly states the action 'Assign an existing role to a member', using a specific verb and resource. Distinguishes from sibling tools like discord_create_role and discord_remove_role.

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 when to use (assign a role) and when not (use discord_remove_role to undo). Provides prerequisites: Manage Roles permission and role hierarchy constraint.

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