Delete a role

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'Irreversible' is a useful but minimal disclosure; it does not explain cascading effects on users assigned to the role, required permissions, or whether deleting a role with dependencies is even allowed. Significant gaps remain 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?

Two short sentences convey the essential action and a key warning. Every word earns its place, with no redundant or vague content.

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 operation with two parameters and no annotations or output schema, the description is too sparse. It does not address what happens to role assignments, error conditions, or whether organization scoping affects the deletion scope, leaving the agent underinformed for high-stakes usage.

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 input schema lists roleId (required) and organization (optional), but schema description coverage is 0%. The description only hints that deletion is 'by id', which maps to roleId, but does not clarify the format of roleId or the purpose of the organization parameter. It fails to compensate for the lack of schema descriptions.

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 a specific verb+resource: 'Delete a role by id'. It distinguishes from sibling tools like wflow_upsert_role (create/update) and wflow_list_roles (read). The addition of 'Irreversible' reinforces the intended destructive action.

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 guidance is provided on when to use this tool versus alternatives, such as wflow_list_roles to find a role ID first or wflow_upsert_role to modify instead of delete. There is no mention of prerequisites or situations where deletion might be inappropriate, leaving the agent to infer usage from the description alone.

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