reorder_roles

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

Discloses reordering behavior and how positions are computed for each method. Missing information on required permissions (Manage Roles) and potential side effects on role hierarchy. No annotations provided.

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 concise sentences with clear structure. First sentence states purpose, second explains the two methods with guidance. No wasted words.

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?

Adequately covers the main functionality and parameter choices. Lacks mention of return value or required permissions. Without output schema, a bit more detail on what happens after reordering would improve completeness.

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?

Adds meaningful context beyond schema: explains the difference between the two mutually exclusive parameters, the preferred usage, and that orderedRoleIds computes positions automatically.

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 it reorders roles and distinguishes from sibling tools like create_role, delete_role, edit_role by focusing on reordering. The two methods (orderedRoleIds and rolePositions) are explicitly described.

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 clear guidance on using orderedRoleIds as preferred method and rolePositions as advanced, and to provide exactly one. However, does not explicitly state when not to use this tool vs edit_role for single role changes.

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