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

Annotations already declare destructiveHint=true and idempotentHint=true, but the description adds real value beyond them: it discloses that the operation overwrites fields and that previous values are not kept, and it documents the owner-role restriction that will reject certain calls.

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?

Three short, dense sentences with no filler. The ordering is slightly awkward (the generic overwrite caveat precedes the statement of what the tool actually does), but everything stated 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 single-purpose mutation with full annotation coverage and no output schema, the definition covers the destructive semantics and the business-rule restrictions. It omits auth/permission requirements and any error behavior, which are minor gaps given what the annotations already convey.

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 description coverage is 100%, so all three parameters (role, user_id, organization_id) are already documented in the schema, including the role enum values and the no-owner restriction. The description restates the role constraints but adds no syntax or format detail 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 names a specific verb and resource: changing a user's role within an organization, plus an explicit field-update statement. It is clearly distinguishable from siblings such as delete-user-tool or list-users-tool, though it does not explicitly contrast with the other update-*-tool tools.

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?

Usage is implied by the constraints stated (allowed roles are admin and member; owner's role cannot be changed; promotion to owner unsupported), which tells the agent when the call will fail. There is no explicit when-to-use vs alternative guidance or routing to a sibling tool.

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