Post delete group member

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

The annotations already declare destructiveHint=true and readOnlyHint=false, so the safety profile is carried by structured metadata. The description adds that exactly one member is removed, but it does not explain permissions, irreversibility, or what happens if the member is not in the group.

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 front-loaded sentence with no filler or repetition. Its brevity is efficient, though it also contributes to the overall under-specification.

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, six-parameter mutation with zero schema descriptions and no output schema, the description is too thin. It gives the core action but omits parameter semantics, permission requirements, and side effects that an agent would need for confident invocation.

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 0%, yet the description does not document org_id, group_id, member_id, or the generic form/params/json_body fields. It only conceptually maps 'group' and 'member', leaving the required organization identifier and the meaning of the other parameters unexplained.

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 action and resource: remove one member from a group. The phrase 'one member' helps distinguish it from bulk member deletion, but it does not explicitly name relevant siblings such as bulk_delete_member or put_group_members.

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 when-to-use guidance, prerequisites, or explicit alternative tool. The agent must infer from the tool name and short description that this is for singular group-member removal rather than bulk or membership-update operations.

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