Delete a Scaleway IAM Group

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

The description goes far beyond what annotations provide (destructiveHint=true). It details the permanent nature, the need for confirm=true, the immediate loss of policy access for former members, and the tool-side check that prevents deletion of special groups. This fully compensates for the lack of behavioral detail in annotations.

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 concise at under 30 words but packs critical information: permanent deletion, confirm requirement, irreversibility, policy impact, and protection for special groups. Every sentence serves a distinct purpose with no fluff.

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 the tool has only 2 simple parameters, no output schema, and high schema coverage, the description is complete. It covers the deletion behavior, required confirmation, downstream effects, and guardrails. Adds exactly what an agent needs to understand the tool's impact beyond the schema.

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 input schema already has 100% coverage with descriptions for both group_id and confirm parameters. The description adds context about the confirm parameter being required for safety but doesn't elaborate on group_id beyond what the schema provides. Baseline 3 is appropriate since schema does the heavy lifting.

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 'PERMANENTLY delete a Group' and emphasizes irreversibility, which is a very specific verb+resource combination. It distinguishes itself from sibling tools like scaleway_iam_create_group or scaleway_iam_update_group by highlighting the permanent destruction aspect.

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 explicitly mentions the required 'confirm=true' parameter for safety, and warns about irreversible consequences including policy access loss. It also states it refuses Scaleway-managed groups (all_users/all_applications) tool-side. However, it doesn't explicitly name an alternative tool for safer deletion or mention when NOT to use it aside from protected groups.

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