discord_set_role_position

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

Discloses permission requirement and position constraint, adding value beyond annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=true). 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, front-loaded action, no redundancy. Each sentence adds essential 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 purpose, permission, constraint, and effect on hierarchy. No output schema, but description is sufficient for a role-position tool with given annotations and schema.

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 describes all 3 parameters (100% coverage). Description adds meaning to 'position' (higher=higher rank) and constraint relative to bot's role, enhancing semantics.

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?

Clear verb+resource: 'Move a role up or down in the server's role hierarchy.' Explicitly distinguishes from siblings by focusing on position manipulation, not creation or property editing.

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?

States required permission (Manage Roles) and constraint (target position below bot's highest role). Does not explicitly mention alternatives, but the context and purpose imply use case.

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