List Scaleway IAM SSH Keys

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

Annotations already declare readOnly, openWorld, idempotent, and not destructive. The description adds valuable behavioral context: it is a compact view that omits the public key text, and it requires specific permissions. No contradictions 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?

Three efficient sentences, each delivering essential information: purpose + context, behavioral trait + alternative, permission requirement. No wasted words, and the most critical information is front-loaded.

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?

The tool is simple with two optional parameters, and the description covers purpose, behavioral limitation, and permission. However, there is no output schema, and the description does not mention what fields are returned (e.g., id, name, creation date). It only says 'compact view' without specifying the return structure, leaving an incomplete picture.

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%, so baseline is 3. The description does not add any meaning beyond what the schema already provides for the two parameters (`name` and `project_id`). It mentions 'Project' in the main text but does not elaborate on parameter behavior.

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 it lists SSH public keys registered in a Project, with a specific verb and resource. It distinguishes itself from the sibling `scaleway_iam_get_ssh_key` by noting it is a compact view that omits the public key text, and explicitly directs users to that tool for full details.

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 a clear alternative (`scaleway_iam_get_ssh_key`) for when the full key is needed, and states the required permission (`SSHKeysReadOnly/FullAccess`). It implies usage context (listing keys for a project) but does not explicitly list exclusions or scenarios where this tool should not be used.

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