Overwrite a Scaleway IAM Group's entire membership

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

Annotations already signal destructive and write behavior. The description adds critical detail: 'anyone currently a member but NOT in either list is REMOVED, losing this group’s grants immediately' and 'Refuses Scaleway-managed/special groups', providing transparency beyond annotations without contradiction.

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 sentences convey the core operation, consequences, requirements, and limitations without any extraneous information. Every sentence earns its place.

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 mutation tool with no output schema, the description covers the key behavioral aspects: full replace, immediate removal, confirm flag, safety restrictions. It does not detail error scenarios or idempotency (covered by annotations), but remains complete enough for 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?

Schema coverage is 100% and descriptions are adequate. The description adds extra semantic value by explaining the cumulative effect of the arrays ('the given user_ids/application_ids become the COMPLETE member list') and practical usage ('Pass empty arrays to remove everyone'), justifying a score above the baseline of 3.

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 'FULL-REPLACE a Group's membership' and clarifies that the provided arrays become the complete member list, distinguishing it from incremental add/remove sibling tools like scaleway_iam_add_group_member and scaleway_iam_remove_group_member.

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 implies when to use (full replacement vs incremental changes) through terms like 'FULL-REPLACE' and 'COMPLETE member list', and provides practical guidance: 'Requires confirm=true', 'Pass empty arrays to remove everyone', and 'Refuses Scaleway-managed/special groups'. No explicit alternatives are named, but the context is clear.

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