hwid_devices_delete_all

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. This is a destructive bulk operation, yet the description offers no warning about irreversibility, side effects, permission requirements, or what happens to related data. This is a serious omission.

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, efficient sentence with no fluff, front-loading the core action. However, it is so terse that it omits crucial behavioral context, making it slightly under-specified for its purpose.

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 destructive bulk delete operation with no output schema and no annotations, this description is dangerously incomplete. It fails to mention irreversibility, potential errors, prerequisites, or any post-condition, leaving an agent without the information needed to safely invoke it.

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 100% with only one parameter (userId) documented as 'User numeric ID'. The description adds no extra meaning beyond the schema, so it earns the baseline of 3 without further credit.

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 states a specific verb+resource: 'Delete all HWID devices for a user.' It clearly distinguishes from the sibling 'hwid_device_delete' (singular) by using 'all', so an agent can tell them apart without ambiguity.

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 is given on when to use this tool versus alternatives like hwid_device_delete for individual devices. It does not mention any conditions, exclusions, or context that would help an agent decide between bulk and singular deletion.

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