Delete role

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

Discloses the two-step deletion process (first call returns preview and confirm_token, second call with token performs deletion) and the effect on members. This adds value beyond the destructiveHint annotation.

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 concise (4 sentences) and front-loaded with the primary purpose. Each sentence adds value; no filler.

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?

Despite explaining the gated flow, the description omits details about the preview output, how confirm_token is obtained, and the role of 'dry_run'. For a destructive tool with 5 parameters and no output schema, it is incomplete.

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?

With only 40% schema description coverage, the description does not elaborate on any parameters. It does not explain the 'reason', 'dry_run', or 'confirm_token' fields, leaving the agent to infer their usage.

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 tool deletes a role and explains the effect (members lose it, nothing else changes). However, it does not distinguish between this tool and sibling tools like 'remove_role', which may have different semantics.

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 guidance on the safe gated flow ('prefer this gated flow over telling the user to delete the role manually'), but does not explicitly state when to use this tool versus alternatives like 'remove_role' or other role modification tools.

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