unifi_bulk_delete_vouchers

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

With no annotations provided, the description carries full burden. It states this is a deletion operation but doesn't disclose critical behavioral traits: whether this is reversible, what permissions are required, if there are rate limits, or what happens on success/failure. The example filter helps but doesn't cover behavioral risks.

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?

Single sentence is appropriately concise and front-loaded with the core action. The parenthetical example is useful but could be slightly more structured. No wasted words.

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 operation with no annotations and no output schema, the description is insufficient. It doesn't cover what happens after deletion, error conditions, or important constraints. The example helps but doesn't compensate for missing behavioral context.

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 100%, so the baseline is 3. The description adds minimal value by providing a filter example ('expired.eq(true)'), but doesn't explain parameter relationships or additional semantics beyond what's in the 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 clearly states the verb ('bulk delete') and resource ('hotspot vouchers'), and specifies the action is based on filter criteria. It distinguishes from sibling 'unifi_delete_voucher' by emphasizing bulk operations with filtering.

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 explicit guidance on when to use this tool versus alternatives like 'unifi_delete_voucher' or 'unifi_list_vouchers'. The description mentions filter criteria but doesn't provide context about when bulk deletion is appropriate versus individual deletion.

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