Remove a member from the group

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

Annotations already declare destructiveHint=true and readOnlyHint=false. The description adds valuable context: requires operator write opt-in and confirm:true, may notify recipients or change tenant data. This goes beyond the annotations and warns the agent about side effects.

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 compact and front-loaded with the action and endpoint. The reference URL and behavioral warnings are useful, though the reference URL could arguably be omitted. Overall, every sentence 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 destructive mutation with no output schema, the description covers the key operational facts: endpoint, required confirm flag, operator opt-in, and potential side effects. It doesn't describe the response format, but the absence of an output schema makes that less critical. The main gap is not explaining what happens if confirm is false, but the schema's const:true already implies it.

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 67%: the confirm parameter is well-documented in the schema, and the path parameters (groupID, memberID) are structurally clear. The description adds the endpoint template showing where groupID and memberID go, which is helpful but not deeply semantic. Baseline 3 is appropriate.

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 ('Remove'), a specific resource ('a member from the group'), and includes the exact REST endpoint. It clearly distinguishes this from sibling tools like xmatters_add_a_member_to_the_group and xmatters_get_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?

The description includes the HTTP method and endpoint, and the confirm:true requirement implies this is a destructive action requiring explicit approval. It doesn't explicitly name alternatives or when-not-to-use, but the endpoint and mutation semantics make the usage context clear.

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