remnawave_hosts_bulk_delete

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

With no annotations, the description carries the full burden, but it only says 'mutation'. It does not disclose destructive behavior, confirmation requirements (confirmToken, mutationApproved), or any other 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 a single sentence, but it lacks substantive content. Conciseness is sacrificed for completeness; it is too terse for a tool with 4 parameters and no schema descriptions.

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 objects, enum, no output schema), the description is utterly incomplete. It fails to explain the payload structure, confirmation flow, or response modes, making it insufficient for correct agent invocation.

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 adds zero parameter information. The 4 parameters (payload, confirmToken, responseMode, mutationApproved) are not explained, leaving the agent without guidance on 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 hosts.bulk_delete (mutation)' indicates a bulk delete operation on hosts, which is somewhat clear but not specific. It does not differentiate from the singular delete tool (remnawave_hosts_delete) or explain what exactly is deleted.

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 context is provided. The description does not specify when to use this tool versus alternatives like remnawave_hosts_delete or other bulk operation tools, nor does it mention prerequisites or conditions.

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