vibemk_delete_user_role

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

There are no annotations to carry safety or side-effect information, so the description bears full responsibility. It states that deletion is limited to custom roles, but does not disclose that deletion is permanent/irreversible, whether roles in use are protected, or what errors might occur.

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 extremely concise and to the point, using one short sentence to convey both the action and the key limitation. No filler or redundant 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 simple delete operation with a single parameter and no output schema, the description is adequately complete. It includes the important built-in-role restriction, though it stops short of describing return values or failure conditions.

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 only parameter, role_id, is fully documented in the schema as 'ID of the custom role to delete'. The description adds no additional meaning beyond restating the schema, but because schema coverage is 100%, the baseline score of 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?

The description clearly states the action ('Delete user role') and the target resource ('custom user role'), and explicitly distinguishes it from built-in roles. This differentiates it from sibling tools like update_user_role or list_user_roles.

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 gives a clear usage constraint: only custom user roles can be deleted, not built-in roles. It does not explicitly point to alternatives for listing or creating roles, but the custom-vs-built-in distinction is enough to guide appropriate use.

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