rm_delete_role

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, and the description adds the critical requirement that confirm=True is mandatory. This goes beyond the annotations by telling the agent the exact safety gate needed to execute the deletion.

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 one concise sentence that front-loads the core operation and the essential safety requirement. There is no filler or redundant restatement.

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 simple two-parameter delete tool with an output schema and destructive annotations, the description covers the critical invocation details: target role and confirm flag. It does not discuss cascading effects or errors, but those are secondary given the annotations and schema.

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 must compensate. It clarifies that confirm must be true to delete, which adds meaning beyond the schema's bare boolean/default. role_id is self-explanatory from the tool name and schema property.

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 uses a specific verb ('Delete') and resource ('a role'), making the operation unambiguous. It clearly distinguishes this tool from sibling create/update role tools.

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 provides a procedural prerequisite ('requires confirm=True') but offers no explicit when-to-use or when-not-to-use guidance. It does not mention alternatives, though no obvious alternative delete tool exists for roles.

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