delete-composite-roles

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

With no annotations provided, the description must disclose behavioral traits. It only says 'Delete composite roles from a role' and does not clarify whether this destroys the composite role entities or just their associations, nor does it mention permissions, reversibility, or side effects. The ambiguity around what is actually deleted is a significant transparency gap.

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 with no filler words. Every word contributes to the core meaning, making it highly efficient and front-loaded.

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 tool has no output schema and no annotations, and the description is extremely brief. It lacks essential context such as prerequisites (e.g., the role must exist), how the 'roles' array should be structured, and what the tool returns. The presence of many sibling role-management tools increases the need for clearer contextual guidance, which is missing.

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?

Schema coverage is 100% (all parameters have descriptions), so the baseline is 3. The description does not elaborate on parameter meaning beyond the schema. The schema's 'Array of roles to remove' is ambiguous, but the description's 'from a role' adds a small clarifier that the removal is scoped to a role. No additional details about role IDs or names are provided.

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 'Delete composite roles from a role' clearly identifies the action (delete) and the resource (composite roles), and the phrase 'from a role' differentiates it from deleting the role itself. However, it does not explicitly distinguish it from sibling tools like 'delete-role' or 'delete-role-by-id', which could cause confusion in edge cases.

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. It does not mention that this is specifically for removing composite role assignments from a role, nor does it advise using 'delete-role' for full role deletion. Sibling tools exist, but no exclusions or recommended contexts are given.

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