Delete a specific role

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

Annotations already declare destructiveHint=true, idempotentHint=true, and readOnlyHint=false, so the safety profile is covered. The description adds one useful piece of context beyond annotations: the required 'manage_roles' permission. It does not, however, warn about irreversibility or what happens to users currently assigned to the role.

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?

Short and front-loaded, but the second sentence ('Deletes a role specified by its ID') is redundant with the first and consumes space that could have carried the missing safety or usage context.

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?

Output schema exists, so return values need no explanation, and annotations cover destructiveness. Still, for an irreversible deletion with a dry-run-by-default safety valve described only in the schema, the description could have flagged the preview/confirm workflow and consequences of permanent removal.

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 description coverage is 100%, so role_id, confirm, and dry_run are all documented in the schema itself. The description only echoes that the role is identified by ID, adding no syntax, format, or interaction detail beyond the schema; baseline 3 applies.

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?

States a specific verb ('Delete') and resource ('role') plus scope ('specified by its ID'), which is enough to distinguish it from siblings like action1_delete_role_user or action1_delete_group. Loses a point because the second sentence largely restates the first rather than adding differentiating detail.

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?

No explicit when-to-use guidance, no mention of alternatives such as action1_update_role or action1_delete_role_user, and no note that this is irreversible. The 'Perm: manage_roles' note is a prerequisite, not usage guidance.

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