hwid_devices_delete_all

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

Annotations already declare readOnlyHint=false and destructiveHint=true, so the safety profile is carried for the agent. The description's 'all' adds a useful scope cue (breadth of the wipe) beyond the annotations, but it says nothing about irreversibility, whether a user's devices can be recreated, or any side effects on active subscriptions/sessions. With annotations doing the safety heavy lifting, this is an adequate but thin addition.

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?

A single five-word sentence that is fully front-loaded with the action and scope, with no filler. It is efficient, though the extreme brevity is under-specification rather than true conciseness for a destructive tool.

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 bulk destructive operation with no output schema and an entirely undocumented required parameter, the description omits the information an agent most needs: irreversibility, whether the userId is required and what it identifies, and confirmation expectations. The annotations cover the safety hint, but the description leaves significant behavioral and parameter gaps unresolved.

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?

There is one parameter (userId) with 0% schema description coverage, so the description needs to compensate. Saying 'user HWID devices' only implicitly ties userId to the scope; it doesn't state that the parameter is the target user's numeric ID or what happens for a user with no devices. Minimal compensation over the bare schema.

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 gives a specific verb ('Delete') plus resource ('all user HWID devices'), so an agent immediately knows this is a bulk destructive operation on a user's device records, distinguishable from the singular 'hwid_device_delete' sibling. It stops short of explicitly naming that sibling or the read-only 'hwid_devices_list' alternative, but the purpose itself is unambiguous.

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 when-to-use guidance is present. The description never clarifies when an agent should call this bulk delete versus the single-device 'hwid_device_delete', nor does it state any prerequisite (confirmation, target user context) before firing an operation that wipes every device for a user.

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