unifi_gen_deletevouchers

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

Annotations already declare destructiveHint=true, idempotentHint=true and openWorldHint=true, so safety framing is covered structurally. The description adds nothing beyond that, and the genuinely consequential behavior - that an unfiltered/broad call could remove many vouchers, and that a preview path exists - is left entirely to the schema's confirm/dry_run fields rather than stated in prose.

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-loads the action, but a single fragment plus a generated-from URL is under-specified rather than concise. The URL segment earns no place for an agent choosing a 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?

A destructive bulk-delete tool with a required, undocumented filter parameter and no output schema needs the description to explain filtering scope and result behavior. Neither is present, so an agent cannot confidently construct a safe call from this definition 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 coverage is 67%, and the one required parameter, "filter", has no description anywhere - neither in the schema nor in the description. The description would need to compensate by explaining the filter syntax or scope (what identifiers are accepted, whether multiple vouchers can be matched), and it does not.

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 Vouchers" names a specific verb and resource, so the basic operation is clear. However, it does not distinguish this bulk delete from the closely named siblings unifi_gen_deletevoucher (singular) and unifi_net_delete_vouchers, and the trailing "generated from developer.ui.com/..." string adds no meaning.

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 or when-not-to-use guidance and no mention of the singular sibling or the alternative list tools. The only implicit cue is destructive intent from the name and annotations.

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