List Scaleway IAM Groups

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

Annotations already provide readOnlyHint=true, destructiveHint=false, idempotentHint=true. The description adds valuable behavioral context: that preset and managed groups are included, and that name filter is exact (not substring). This goes beyond annotations without contradicting them.

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 with no fluff. First sentence states purpose and scope; second provides critical filtering nuances. Every word earns its place. Excellent structure.

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 6 optional parameters and no output schema, the description covers filtering nuances but omits pagination details, default ordering, response format, or what happens with no filters (returns all groups). While sufficient for a simple read-only list tool, minor gaps prevent a higher score.

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 83%, so baseline is 3. The description adds that name is an exact match and array filters use ANY logic, which partially repeats schema descriptions. It does not clarify tag exactness (already in schema) or order_by. The added value is marginal, meeting but not exceeding the baseline for high-coverage 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 uses a specific verb ('List') and resource ('Groups'), and clarifies scope ('in the Organization, including Scaleway's preset groups and any special managed groups'). This clearly identifies the tool's purpose and distinguishes it from sibling tools like list_users or create_group.

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 implicit usage guidance by detailing filter behavior ('name is an EXACT match', 'Array filters narrow to groups matching ANY of the given ids'). However, it does not explicitly state when to use this tool vs alternatives (e.g., get_group for a single group) or when not to use it. The guidance is present but not comprehensive.

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