remove_participants

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

With no annotations provided, the description carries the full behavioral burden and falls short. It does not say that this is a mutating, effectively destructive operation, whether removals are reversible, what permissions are required, or what happens if a listed participant is not in the group. For an opaque 2-parameter mutation tool this is a meaningful disclosure gap.

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?

A single short, front-loaded sentence with no filler. It is efficient, though it is arguably under-specified rather than genuinely concise, which keeps it out of the top band.

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 annotations, no output schema, and 0% parameter documentation, the description is far too thin. An agent would need external knowledge about the Zappaz API to call it correctly, so the definition is not self-sufficient.

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%, so the description must compensate and it does not. It never explains that 'data' is an array of participant identifiers (or what form those take) or what 'groupId' refers to, leaving both required parameters semantically undocumented.

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 gives a specific verb ('remove') plus resource ('participants from a group'), which clearly separates it from siblings like add_participants, promote_participants and demote_participants. It doesn't explicitly name those alternatives, but the action itself is unambiguous. Only a slight deduction for not stating scope limits (e.g. bulk vs single removal).

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 tool versus the adjacent participant-management siblings (add, promote, demote). No prerequisites, no mention of who is allowed to remove participants, and no conditions or exclusions are given. The agent must infer usage entirely from the name.

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