remnawave_external_squads_add_users

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

With no annotations, the description must disclose behavioral traits. It only labels the tool as a 'mutation' but provides no details on what state changes occur, whether permissions are required, or how confirmToken and mutationApproved affect execution.

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 is not concise in a helpful way—it is under-specified and lacks necessary details. It fails to communicate the tool's purpose or usage.

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 tool's complexity (4 parameters, 0% schema coverage, no output schema), the description is woefully incomplete. It provides no information about return values, side effects, or how to structure requests.

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 coverage is 0% and the description adds no meaning to the parameters. The payload object with additionalProperties is especially vague; the agent cannot know its expected structure or content without explanation.

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 'Remnawave external_squads.add_users (mutation)' is a tautology that merely restates the tool name. It does not specify what action is performed (e.g., adding users to a squad) or distinguish it from siblings like remnawave_external_squads_create or remnawave_external_squads_remove_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?

There is no guidance on when to use this tool versus alternatives. For example, it doesn't explain the difference between external and internal squads, or when adding users is appropriate versus creating or removing them.

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