delete_role

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

The description discloses an important side effect: deleting the role also deletes its row-level/object-level rules and members. However, with no annotations provided, it does not mention whether the operation is irreversible, what permissions are required, or how it behaves if the role does not exist.

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 a single sentence, front-loaded with the main verb 'Delete', and includes critical scope information about cascading deletion without unnecessary words.

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 covers the core purpose and a key side effect, making it adequate for a simple delete tool. However, it lacks usage guidance, parameter semantics, and any mention of error conditions or prerequisites, leaving notable gaps.

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?

Both parameters are required but the description offers no details about them. 'name' is somewhat self-explanatory as the role name, but 'sessionId' is unclear. With 0% schema description coverage, the description should compensate, but it does not.

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 tool deletes a security role and explicitly notes it also removes associated row-level/object-level rules and members. This specific verb+resource+scope distinguishes it from sibling tools like remove_role_member or delete_measure.

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 remove_role_member or set_role_permission. The description implies use when deleting a role but does not specify exclusions, prerequisites, or cases where another tool would be more appropriate.

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