List Scaleway IAM Permission Sets

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

The description adds valuable behavioral context beyond the readOnlyHint and idempotentHint annotations by explaining that each permission set has a scope_type ('organization' or 'projects') and that combining different scope_types causes a 400/invalid_arguments error. This details the data model and failure mode without contradicting the 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 a compact three-sentence paragraph that efficiently covers the tool's purpose, a critical domain constraint, and usage guidance. Each sentence earns its place with no redundant information or filler.

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 list tool with one optional filter and no output schema, the description is self-contained: it explains what is listed, the important scope_type constraint, and the recommended workflow with scaleway_iam_create_policy. It also gives the exact error message, making it sufficiently complete for safe and effective use.

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 only parameter, name_filter, is already fully described in the schema with examples like 'ObjectStorage' or 'IAM', achieving 100% schema description coverage. The tool description adds no additional parameter-level meaning, so it remains at the baseline for fully documented schemas.

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 explicitly states 'List every permission set Scaleway IAM policies can grant' with concrete examples like ObjectStorageReadOnly and IAMPolicyManager. This clearly identifies the tool's function and distinguishes it from sibling IAM tools like scaleway_iam_list_policies.

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 gives explicit usage guidance: 'Call this BEFORE scaleway_iam_create_policy to confirm exact names and scope_types'. It also warns that mixing scope_types in a single rule fails with a specific error and advises using separate rules, providing actionable context for when to use this tool.

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