remnawave_internal_squads_remove_users

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

No annotations exist, so the description must fully disclose behavior. It only states it's a mutation, which is already evident. It does not mention the need for a confirmToken, the effect of mutationApproved, or any side effects like cascading removals.

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?

While extremely short, the description fails to be informative. Every sentence should add value, but this single sentence adds none beyond the tool name.

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?

Given the complexity (nested payload, confirmation token, response mode), the description is grossly incomplete. With no annotations or output schema, the agent cannot understand preconditions, effects, or response format.

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%, and the description provides zero explanation of the four parameters (payload, confirmToken, responseMode, mutationApproved). The agent gains no insight into how to structure the payload or use the confirmation flow.

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?

Description is a tautology, restating the tool name and adding '(mutation)'. It does not specify which users are removed from which squad, nor distinguish it from the sibling tool 'remnawave_internal_squads_add_users'.

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?

No guidance on when to use this tool versus alternatives like remnawave_external_squads_remove_users or remnawave_internal_squads_add_users. No context for prerequisites or when not to use.

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