alterios_delete_role

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

The description labels the tool as 'security/destructive write', which hints at potential irreversible actions, but it does not disclose key behaviors such as what happens on actual deletion, the role of dry_run, or whether the operation can be undone. No annotations are provided to supplement this.

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 very concise at two sentences, presenting the core information without waste. However, it could be slightly expanded to cover important details without becoming verbose.

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 write tool with 6 parameters and an output schema, the description is severely lacking. It does not explain the planning versus deletion workflow, parameter roles, or return values, leaving the agent underinformed.

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 description adds no meaning to any of the 6 parameters. With 0% schema coverage, the description fails to explain parameters like dry_run, expected_name, or allow_destructive, which are critical for correct usage.

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's action ('Plan or delete') and resource ('Alterios role'), and it distinguishes itself from sibling tools like alterios_list_roles (listing) and alterios_upsert_group (update/create).

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, when not to, or what alternatives exist. For example, it does not explain when to plan versus delete, nor does it mention prerequisites like required permissions.

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