Delete Group Iteration Cadence

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

Annotations already declare destructiveHint=true and idempotentHint=false, so the description earns credit for what it adds: 'permanently' and 'Irreversible' confirm no undo, and 'and its iterations' discloses cascade scope that annotations do not express. Tier requirement is also disclosed. Not full marks because it says nothing about permission/ownership needs or failure behavior.

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?

Four short fragments, front-loaded with the destructive action and its irreversibility, then constraints, then the pre-check pointer. Nothing is wasted and nothing important is buried.

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 two-parameter destructive tool with no output schema, the description covers permanence, cascade effect, required inputs, a discovery path, and tier availability. Remaining gap is minor: no note on authorization level or what a failed delete returns.

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 description coverage is 0%, so the description must carry parameter meaning. It only restates that group_id and iteration_cadence_id are required — information already in the schema's required array — with no guidance on ID format (numeric vs path) or how to obtain the cadence ID beyond the list call.

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?

States a specific verb and resource (delete an iteration cadence) and adds scope that separates it from the sibling that deletes a single iteration: 'and its iterations' signals a cascade on the parent cadence. An agent can distinguish it from gitlab_delete_group_iteration without opening either schema.

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?

Points to a concrete sibling pre-check (gitlab_list_group_iteration_cadences) and flags the Premium/Ultimate tier requirement, which is real usage context. It stops short of saying when not to use this or what to do instead when only one iteration should be removed, so no explicit exclusion.

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