remnawave_hwid_delete_all_devices

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

No annotations are provided, and the description does not disclose any behavioral traits such as irreversibility, authorization needs, or the role of parameters like 'confirmToken' and 'mutationApproved' in controlling the operation.

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 this is due to underspecification rather than conciseness. It fails to provide necessary information, so brevity here is a drawback.

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 tool's complexity (4 parameters, nested object, no output schema, no annotations), the description is woefully incomplete. An agent cannot determine how to construct a valid request or interpret the result.

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 offers no explanation for any of the four parameters. The 'payload' object, 'confirmToken', 'responseMode', and 'mutationApproved' remain completely undocumented, leaving the agent without guidance on how to properly invoke the tool.

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 name as 'Remnawave hwid.delete_all_devices (mutation).' It does not clarify what scope the deletion applies to (e.g., all devices for a specific user or globally). Compared to sibling 'remnawave_hwid_delete_device,' the differentiation is implied but not explained.

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 instructions on when to use this tool versus alternatives like 'remnawave_hwid_delete_device.' There is no mention of prerequisites, confirmation requirements, or context where bulk deletion is appropriate.

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