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

Annotations already declare non-destructive, idempotent, open-world behavior. The description adds substantial operational context: login requirement, OWNER/ADMIN permission gating, special immutability rules for owners and platform-designated roles, and the critical distinction that membershipId is not userId.

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?

Uses bracketed labels to front-load authentication, roles, the call chain, and pitfalls. Every line carries an actionable constraint; despite being dense, there is no redundant 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 mutation tool with no output schema, the description covers the permission model, prerequisite lookup, confirmation step, and invalid cases. An agent has everything needed 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 coverage is 100%, so the baseline is 3. The description maps role enum values to Chinese labels and warns that membershipId differs from userId, but most of this repeats the schema's own descriptions rather than adding new format or constraint detail.

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?

States a specific verb and resource: setting an enrolled member's role to one of four named roles. It also names the login/permission gate (OWNER/ADMIN) up front, so an agent can immediately distinguish it from sibling tools like remove_organization_member or update_my_organization_membership.

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?

Gives an explicit invocation chain: call list_organization_members to obtain membershipId, read it back to the user for confirmation, then call this tool. It also lists when-not conditions, such as owner roles being immutable and only the owner being able to change ADMINs.

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