remnawave_users_update

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

No annotations are present, so the description must fully disclose behavior. It only labels the tool as a 'mutation,' indicating state change, but provides no details on required permissions, side effects, or error conditions.

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 concise (one sentence), but severely under-specified for a tool with four parameters and no schema descriptions. This is not effective conciseness; it is minimalism that harms usability.

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 of the tool (mutation with a free-form `payload` object and approval mechanism) and the lack of annotations and output schema, the description is wholly inadequate. It fails to explain how to construct inputs, what the tool returns, or how it integrates with other tools.

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%, meaning no parameter descriptions exist, and the description adds no information about the four parameters (`payload`, `confirmToken`, `responseMode`, `mutationApproved`). The agent has no guidance on how to use these parameters.

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 'Remnawave users.update (mutation)', clearly indicating it updates users. This distinguishes it from read-only tools, but it does not differentiate from sibling tools like `remnawave_users_bulk_update` without additional context.

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 usage guidelines provided. The description does not specify when to use this tool versus alternatives like `remnawave_users_bulk_update` or `remnawave_users_create`, nor does it mention prerequisites or context.

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