superset_role_delete

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

With no annotations, the description carries the full burden of behavioral disclosure. It explains the consequential effect (users lose permissions) and emphasizes that confirm_delete is required. However, it does not state whether deletion is permanent or irreversible, which is a notable omission for a destructive operation.

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 compact and well-structured, with a one-line purpose, a clear blocklist, and an Args section. Every sentence provides necessary information without redundancy or fluff.

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 destructive delete tool, the description covers the key aspects: what it does, the consequence, and a critical safety parameter. It does not mention return values, but an output schema exists. The minor gap is lack of clarity about irreversibility and the confirm_delete requirement conflict with the 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?

The description adds meaning by naming and explaining role_id and confirm_delete beyond the bare schema. However, calling confirm_delete 'REQUIRED' contradicts the schema's required list (only role_id is required) and default value (false). This inconsistency could mislead an agent about whether the parameter must be supplied or set to true.

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 a clear verb and resource: 'Delete a role.' It further clarifies the impact ('Users with this role will lose the associated permissions'), which distinguishes it from related role tools like update or create. The purpose is unmistakable and specific.

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 a when-not condition by listing system roles that are blocked from deletion. It does not name alternative tools, but the delete operation is distinct enough that the lack of explicit alternatives is acceptable. The context is clear for when to use this tool.

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