delete_role

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

With no annotations provided, the description carries the full behavioral disclosure burden. It reveals the preview-by-default mechanism, the confirm flag, and the requirement to pass the preview's expected value. It does not detail side effects or irreversibility, but the deletion preview behavior is well disclosed.

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 short sentences, each carrying distinct and necessary information: the action, the preview/confirm workflow, and a critical safety guardrail. No filler or repetition.

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?

The description gives the essential safety-critical workflow and is fairly complete for a DELETION tool with an output schema. However, it leaves the meaning and structure of 'expected' somewhat vague and does not mention the optional 'why' parameter, which could be relevant for audit or justification. There is enough for basic calling but not full parameter comprehension.

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 0%, so the description should compensate by explaining parameters. It only hints at confirm and expected through 'Preview unless confirm=true with the preview's expected.' role_id and why are not explained at all, leaving the agent to infer their meaning from the schema alone.

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 opens with the specific verb-resource pair 'Delete a role,' making the tool's core purpose immediately clear. It also clarifies an important behavior—preview by default, delete only with confirm—so it is not confused with a plain destructive delete.

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 explicitly states when not to call the tool: 'Do not call unless the user explicitly asked to delete this role' and 'Findings are not a reason to delete.' This is strong, unambiguous usage guidance even though no alternative tool is named.

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