remnawave_nodes_bulk_actions

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

The only behavioral hint is '(mutation)', indicating state change. However, no details are given about side effects, destructive potential, or required permissions. With no annotations, the description fails to disclose crucial behavioral traits.

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 necessary detail, making it under-specified rather than concise. It does not earn its place as it provides almost no utility.

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 a bulk action tool with a nested payload, no output schema, and many sibling tools, the description is grossly incomplete. The agent cannot determine how to invoke the tool 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%, yet the description adds no explanation for any parameter (payload, confirmToken, responseMode, mutationApproved). The agent receives no help understanding what these parameters do.

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 states 'Remnawave nodes.bulk_actions (mutation)', which vaguely indicates it performs bulk actions on nodes but lacks specificity about which actions (e.g., delete, disable, update). It barely distinguishes from sibling tools like nodes_bulk_update or nodes_disable.

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 provided on when to use this tool versus individual node operations or other bulk tools. The description does not mention alternatives or conditions for use, forcing the agent to guess.

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