remnawave_users_bulk_update

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 does not explain side effects, authorization needs, or the role of confirmToken and mutationApproved. The agent cannot infer behavioral implications.

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 lacks essential information, making it under-specified rather than concisely informative. It fails to earn its place by not adding value 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 (4 parameters, nested object, no output schema, no annotations), the description is grossly incomplete. It does not cover what the tool does, how to use confirmToken/mutationApproved, or what the response looks like.

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 provides zero explanation for any parameter. The payload is an opaque object with additionalProperties, yet no hint is given about its structure or expected fields.

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 'Remnawave users.bulk_update (mutation)' is nearly a tautology, restating the tool name and type. It does not specify the resource being updated (e.g., which user fields) or distinguish from sibling tools like remnawave_users_bulk_all_update.

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 other bulk user tools such as remnawave_users_bulk_delete or remnawave_users_bulk_extend_expiration_date. The description omits any conditions, prerequisites, or alternatives.

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