discord_set_role_position

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

Annotations indicate it's non-read-only, non-destructive, and idempotent. The description adds context: explains that position affects hierarchy ordering and member list, and notes the permission and bot role constraint. 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?

Three sentences, no redundancy. First sentence defines purpose and effect, second clarifies ranking meaning, third lists prerequisites. Every sentence adds value.

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, effect, permission, and a constraint. No output schema, so return value is not described, but for a simple reposition action this is adequate. Could mention potential cascading changes but is sufficient for agent decision-making.

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 covers all three parameters with descriptions (100% coverage). The description restates that position is a hierarchy value but adds no new parameter details beyond the schema. Baseline 3 is appropriate.

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 ('Move a role up or down'), the resource ('role'), and the context ('server's role hierarchy'). It explains the effect on permission precedence and member-list ordering, distinguishing it from sibling tools like discord_add_role or discord_edit_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?

Provides explicit permission requirement ('Requires the Manage Roles permission') and a constraint ('target position must be below the bot's highest role'). Lacks explicit differentiation from alternative tools when the goal is to change role permissions or edit role properties, but overall clear on when to use.

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