discord_move_role

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

It discloses a key constraint (must be below bot's highest role) but omits other behavioral aspects such as required permissions (e.g., Manage Roles), side effects (e.g., reordering of other roles), and error conditions. With no annotations, the description carries the full burden and only partially covers it.

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?

The description is a single, concise sentence with no fluff, front-loading the verb and resource. However, its brevity sacrifices necessary detail, so it earns a high but not perfect score.

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 with a critical constraint and an ambiguous position parameter, the description is insufficient. It doesn't explain how position is interpreted, what permissions are needed, or what happens if the constraint is violated. The presence of an output schema doesn't compensate for these 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?

Schema coverage is 0% and the description offers no parameter-specific explanation. The 'position' parameter is ambiguous (index? relative? zero-based?), and 'guild_id' and 'reason' are not clarified. The description adds zero semantic value to the parameters.

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) and resource (role), and the constraint about the bot's highest role distinguishes it from other role tools like edit_role or assign_role. It is unambiguous and specific.

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?

The description implies usage conditions (role must be below bot's highest role) but does not explicitly mention alternatives or when not to use this tool. It lacks a direct comparison to sibling tools like discord_edit_role.

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