unifi_gen_deletevoucher

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

Annotations already declare destructiveHint=true, idempotentHint=true, and openWorldHint=true, so the risk profile is known from structured data. The description adds nothing beyond that: it does not mention irreversibility, the confirm/dry_run safety gate, or the effect on active vouchers. No contradiction with annotations, but no value added either.

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?

It is short, but that is under-specification rather than conciseness. The only substantive content is a generated-from URL, which is metadata noise for an agent deciding how to call the 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 destructive, open-world mutation with no output schema and only partial schema coverage, the description should carry real weight but carries none. An agent gets no information about what exactly is removed, whether the operation can be undone, or how the preview/confirm flow behaves beyond what the schema hints at.

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 67%, but the description itself explains none of the three parameters. Notably it does not mention that voucherId is a UUID, that confirm must be literally "YES" for the delete to be applied, or that omitting it returns only a preview – the most consequential semantics of the call.

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?

"Delete Voucher" merely restates the tool name; the only other content is a source-document URL. It never distinguishes this tool from the many nearby siblings such as unifi_net_delete_voucher, unifi_net_delete_vouchers, and unifi_gen_deletevouchers, so an agent cannot tell which delete to pick from the description.

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?

There is no guidance on when to use this tool, when to prefer the singular/plural or net/gen variants, or what prerequisites apply. The URL pointer to developer.ui.com is documentation provenance, not usage guidance.

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