whatsms_admin_delete_role

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

With no annotations provided, the description carries full responsibility for behavioral disclosure. It only states that a role/function is deleted, without mentioning irreversibility, potential impacts on users or permissions, or any failure conditions. For a destructive mutation tool, this leaves the agent unprepared for side effects.

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, concise sentence that directly states the tool's purpose. No filler or irrelevant information, and it is appropriately sized for the simple operation.

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?

Given that this is a destruction tool with no annotations, no output schema, and an empty input schema, the description is too sparse. It omits crucial information such as how to specify the role, what response to expect, and any prerequisites or side effects. The sibling tool list provides some context, but the description itself is not self-contained.

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 tool has zero defined parameters and an open schema (additionalProperties: true), which is unusual for a delete operation. The description does not clarify how to identify which role/function to delete (e.g., by ID, name), so the agent must infer this. The baseline for zero parameters is 4, but the lack of clarity about how to specify the target drops it to 3, as the description fails to compensate for the schema's emptiness.

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) and the target resource (a role/function) within the WhatSMS system, which is specific and distinguishes it from sibling tools like create_role or update_role. The verb-resource pairing leaves no ambiguity about the tool's primary function.

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 no guidance on when to use this tool versus alternatives, such as when a role should be deleted, prerequisites (e.g., whether the role must be unused), or consequences. It merely states the action itself without any usage context or exclusions.

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