Delete Scaleway API Key

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description goes beyond this by explicitly stating 'PERMANENTLY revoke', 'Irreversible', and the immediate authentication impact. It also flags the required confirmation step. This adds valuable context that annotations alone do not provide.

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?

Two short, front-loaded sentences. No wasted words. Every sentence adds unique value: the first states the action and input, the second states the requirement and consequence.

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 is a simple delete operation with 2 parameters, 100% schema coverage, no output schema, and clear annotations, the description is fully complete. It covers the essential behavioral context (destructiveness, confirmation requirement, immediate effect) that an agent needs.

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%, so baseline is 3. The description adds value by explaining the purpose of confirm ('Must be explicitly true. Deletion is immediate...'), but it does not detail the access_key parameter format beyond what the schema provides (e.g., the 'SCWXXXXXXXXXXXXXXXXX' example is in the schema, not the description). A small deduction for not reiterating the format.

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 uses a strong verb ('PERMANENTLY revoke') paired with a specific resource ('an API key by its access_key'). It is clearly distinct from siblings like scaleway_iam_list_api_keys, scaleway_iam_create_api_key, scaleway_iam_update_api_key, and other delete tools (e.g., scaleway_iam_delete_application).

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 says 'Requires confirm=true' and emphasizes that the action is 'Irreversible - anything using this key stops authenticating immediately.' This gives clear when-to-use guidance and warns against accidental use. It is properly differentiated from list/create/update API key siblings.

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