remove_member

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, and openWorldHint=true, so the safety profile is partly covered. The description adds nothing beyond the name: no permission requirements, no note on whether the member loses workspace access or only group membership, and no statement about repeat-call behavior despite idempotentHint=false. There is a mild tension between 'Delete' and destructiveHint=false, though removing a group membership while preserving the user account is a defensible reading.

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 short phrase with zero redundancy, which is efficient, but it is under-specified rather than genuinely concise, and capitalized like a title rather than a usable instruction.

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 two-parameter mutation, the schema covers inputs and the annotations cover the safety flags, so the core information an agent needs is present. Gaps remain around permissions, failure modes (member not in group), and side effects, which the description does not address.

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%: both group_id and email are documented in the schema as the target group ID and target member email. The description adds no further semantics (e.g., that email must match an existing workspace member), so the baseline 3 applies.

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 ('Delete') and resource ('Member From User Group'), so an agent can tell it removes a group membership rather than a workspace account. It does not, however, distinguish itself from close siblings such as add_member or update_workspace_member beyond the obvious verb flip.

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?

There is no guidance on when to use this versus alternatives (e.g., get_workspace_members to inspect membership, update_workspace_member to change roles, or a workspace-level removal). Usage is only implied by the verb, with no prerequisites or exclusions stated.

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