wafle_members_update_role

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

Annotations already indicate idempotent and non-destructive behavior. The description adds the owner role requirement and lists the updatable fields (role, scopes, is_active). It does not disclose side effects such as whether updating role resets scopes, but with annotations covering the safety profile, this is acceptable.

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 single sentence that front-loads the action, includes the target resource, and mentions the permission requirement. Every word is useful, with no redundancy 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 5-parameter update tool with no output schema, the description covers the action, permission requirement, and which fields can be updated. It does not specify return value or edge cases, but given the tool's simplicity, this is adequately complete for an agent to invoke it correctly.

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 descriptions cover tenant_slug, user_id, and scopes, but role and is_active lack descriptions. The description only repeats the field names without explaining the role enum or is_active semantics. With 60% schema coverage, the description fails to compensate for the missing parameter explanations, adding minimal value beyond the 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 clearly states 'Update a member's role / scopes / is_active for a given tenant' with a specific verb (update) and resource (member). It is distinguishable from sibling tools like wafle_members_list which only lists members, and there is no other member update tool in the sibling list.

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 explicitly notes 'Requires `owner` role on the tenant', providing a clear precondition for use. It does not mention alternatives or exclusions, but given the sibling list, there is no comparable update tool, so the usage context is clear enough without further comparison.

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