unifi_gen_createvouchers

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

Annotations already declare destructiveHint=true, idempotentHint=false and openWorldHint=true, so the description must add context such as what a voucher is for, whether creation is reversible, or the confirm/preview safety flow. It adds only a docs link, leaving the destructive write behavior entirely to the annotations.

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 and front-loaded with the verb+resource, but the second half is a provenance note rather than information an agent can act on. Concise, yet thin rather than efficient.

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?

This is a destructive, non-idempotent creation tool with no output schema, and the description supplies none of the missing context — no return value expectations, no effect of creating multiple vouchers via count, no explanation of the preview/confirm flow. An agent cannot confidently select or call it from this text alone.

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 schema already documents body fields, the confirm token, and dry_run. The description adds no parameter meaning beyond that, which is the expected baseline when the schema does the work.

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?

"Generate Vouchers" names a verb and resource, so the basic intent is clear, but it is essentially a restatement of the tool name plus a docs URL. It does nothing to distinguish this from sibling unifi_net_create_vouchers, which appears to do the same thing.

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 when-to-use guidance at all: no mention of when to pick this over unifi_net_create_vouchers or unifi_net_list_vouchers, and no prerequisites. The only routing hint is a URL to external vendor documentation.

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