Update a Scaleway IAM User

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

Annotations already indicate idempotentHint=true, readOnlyHint=false, destructiveHint=false. The description adds that invalid fields are rejected with the API's own validation message and that only passed fields change. This provides useful context beyond annotations, though it doesn't detail error handling or side effects for mutation of mutable fields.

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 two sentences, concise and front-loaded with the core purpose. Every sentence adds value: the first defines the action and scope, the second clarifies partial update semantics and validation behavior.

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 mutable update tool with no output schema, the description adequately covers partial update behavior and validation, but lacks parameter explanations. Given the 0% schema coverage and 4 parameters, it is incomplete without providing parameter meanings.

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 0% — the description does not explain any parameters, while the schema lists 4 parameters (tags, user_id, last_name, first_name) with types but no descriptions. The description mentions 'tags; name/email' but fails to map to specific parameters, leaving the agent guessing about field names vs schema keys.

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 updates a User's mutable profile fields, specifying tags, name, and email. It identifies the resource (Scaleway IAM User) and action (update), and distinguishes from siblings like create_user, delete_user, lock_user, unlock_user, update_user_password, and update_user_username.

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 partial update behavior ('Only passed fields change'), which helps the agent understand how to use it. However, it does not explicitly state when to use this tool vs alternatives like update_user_username or update_user_password, nor does it mention prerequisites like needing the user_id.

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