remnawave_users_bulk_delete

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

Annotations are absent; the description only labels it a 'mutation' but fails to disclose destructive behavior, safety mechanisms (confirmToken, mutationApproved), or consequences. Critical transparency is missing.

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 extremely brief, the description is under-specified—it sacrifices essential content for brevity. A single sentence that adds no functional value is not effective conciseness.

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 deletion tool (with safety parameters and no output schema), the description provides virtually no context. Return values, prerequisites, and behavior are entirely absent.

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 description, the agent receives no meaning for payload, confirmToken, responseMode, or mutationApproved. Entirely reliant on schema structure alone.

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 users.bulk_delete (mutation)' essentially restates the tool name with 'mutation' clarification. It does not specify what users are deleted or provide any actionable purpose beyond the name itself.

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 vs. alternatives like remnawave_users_delete or remnawave_users_bulk_delete_by_status. The description lacks any context about intended use cases.

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