remnawave_users_bulk_delete_by_status

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

No annotations are provided, and the description only says 'mutation.' Important behavioral details such as destructive nature, required permissions, safety checks (e.g., confirmToken, mutationApproved fields) are not explained. The description adds no transparency beyond the schema defaults.

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 fails to convey essential information. Conciseness is not beneficial when critical details are omitted. The single sentence does not front-load actionable content.

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 zero schema coverage, no output schema, and the presence of many related sibling tools, the description is wholly insufficient. The agent cannot determine the tool's purpose, input requirements, or output behavior. Complete improvement is needed.

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 does not explain any parameter. The payload object (likely containing status or filter criteria), confirmToken, responseMode, and mutationApproved are completely undocumented, leaving the agent without guidance on how to correctly construct the input.

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 merely restates the tool name as 'Remnawave users.bulk_delete_by_status (mutation).' It indicates a mutation operation but does not clarify what 'status' means (e.g., active, expired) or what the tool actually does beyond deleting users by some status. This is barely above a tautology.

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 compared to sibling tools like remnawave_users_bulk_delete, remnawave_users_bulk_disable, or other status-based operations. No prerequisites or alternatives are mentioned.

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