remnawave_nodes_delete

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

The description only labels the tool as a mutation, but without annotations, it fails to disclose critical behaviors such as irreversibility, required permissions, or side effects. The schema hints at confirmation tokens, but the description ignores these.

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 very short, the description is under-specified rather than concise. It sacrifices necessary information, making it less useful than a slightly longer but informative description.

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?

For a mutation tool with 4 parameters, no output schema, and no annotations, the description fails almost entirely to explain what the tool does, how to use it, or what the outcome will be.

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?

With 0% schema description coverage and no parameter descriptions in the tool description, the agent gains no understanding of what the 'payload', 'confirmToken', 'responseMode', or 'mutationApproved' parameters mean or how to use them.

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 nodes.delete (mutation)' essentially restates the tool name, adding minimal clarity. It does not specify what a node is or what deletion entails, leaving the purpose vague.

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 alternatives like remnawave_nodes_disable or remnawave_nodes_bulk_actions. The description lacks any context for decision-making.

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