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

Annotations already declare destructiveHint=true and readOnlyHint=false, so the destructive nature is covered. The description adds useful behavioral context that userId equal to your own means leaving the organization, but it does not disclose permission requirements, irreversibility, or effects on resources owned by the removed member.

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 definition is a single tight sentence with the main action front-loaded and the self-leave special case immediately after. There is no wasted text.

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 destructive two-parameter mutation with no output schema, the description covers the core action and the self-leave behavior. However, it omits important operational context such as required role/permissions, whether the action is reversible, and where to obtain the target userId.

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 50%: orgId is documented as coming from org_list, while userId has no schema description. The description partially compensates by explaining that userId set to your own account changes the operation into a self-leave, but it does not explain how to obtain another user's ID or any other userId constraints.

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 states a specific verb and resource ('Removes a member from the organization') and adds the important special case of self-removal as leaving. It is clearly distinguishable from siblings like org_member_set_role and org_member_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 implies when to use the tool by naming the removal action and the self-leave case, but it does not explain when to choose this over alternatives such as org_invite_revoke, nor does it state prerequisites like admin/owner permissions.

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