Vouchers

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds nothing beyond them — no note on caching (the 'fresh' flag), pagination behavior, or what the listing represents.

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, but that brevity comes at the cost of substance rather than from disciplined editing. There is no wasted sentence, yet no informative one either.

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?

With no output schema, the description should say what a call returns (a paginated list of sold vouchers, with which fields). Instead it leaves the return shape and the distinction from voucher_orders entirely unaddressed.

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?

All three parameters (page, per_page, fresh) are fully documented in the schema with defaults and bounds, so the baseline of 3 applies. The description contributes no additional meaning about pagination or cache semantics.

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 text is a noun fragment that essentially restates the title, with only a small elaboration ('gift cards and packages sold') hinting at scope. It supplies no verb and does nothing to distinguish this tool from close siblings like voucher_orders or voucher_templates.

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 statement of when to use this endpoint versus voucher_orders, voucher_templates, or the payment/checkout tools. An agent must infer from the name alone that this lists sold vouchers rather than orders or templates.

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