remnawave_users_bulk_update_squads

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

The description only says 'mutation', which is already implied by 'update'. It fails to disclose whether the operation is additive or replaces squads, if confirmation is required (despite confirmToken and mutationApproved parameters), or what side effects occur. No annotations exist to cover this 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?

The description is extremely short but fails to convey essential information. Effective conciseness retains necessary detail; here, the brevity results in 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?

With 4 parameters, no output schema, and no annotations, the description is woefully incomplete. It does not explain the tool's role within the broader squad/user ecosystem, leaving the agent without enough context to use it correctly.

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. It does not explain any of the four parameters (payload, confirmToken, responseMode, mutationApproved) beyond what the schema's property names imply. The purpose of payload and the confirmation workflow are completely opaque.

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 only restates the tool name and labels it as a mutation. It does not explain what 'squads' refers to (internal/external) or what updating squads for users entails. Siblings include multiple squad tools, but no differentiation is provided.

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 is given on when to use this tool versus alternatives like remnawave_external_squads_update or remnawave_users_bulk_update. There is no mention of prerequisites or exclusions.

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