Delete Scaleway API Key

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

Although annotations already mark destructiveHint=true, the description adds meaningful context by stating the operation is 'PERMANENTLY' and 'Irreversible' and that 'anything using this key stops authenticating immediately.' This goes beyond the raw annotation and informs the agent of real-world side effects. No contradiction with 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 three short, front-loaded sentences: the action, the required confirm flag, and the irreversible consequence. Every sentence earns its place, with no redundant or filler language.

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 simple, fully schema-documented, two-parameter destructive tool with no output schema, the description provides the essential semantics: what is deleted, the required confirmation, and the immediate effect. Together with the annotations and schema, the agent has sufficient context to invoke the tool safely.

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 100%: the schema already documents access_key as the key identifier (not secret_key) and confirm as a required true constant. The description re-emphasizes these but adds no new semantic detail beyond the schema, so it meets the baseline for a fully covered schema.

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 opens with 'PERMANENTLY revoke an API key by its access_key,' which uses a specific verb and resource and clearly distinguishes this from sibling tools like scaleway_iam_create_api_key or scaleway_iam_update_api_key. It also conveys the destructive nature of the operation, leaving no ambiguity about what the tool does.

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 states the tool is for permanently revoking an API key and requires confirm=true, giving a clear invocation condition. However, it does not explicitly name alternatives or exclusions among the many IAM sibling tools, so the guidance is contextually clear but not fully explicit.

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