Voucher templates

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

The description discloses nothing beyond the name: not what a voucher template is, whether the list is paginated, filtered by business, or cached. Annotations already carry readOnly/idempotent/openWorld hints, so the description's only job is added context, and it adds none.

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?

Two words is technically terse but reflects under-specification, not conciseness; there is no front-loaded content because there is no content. A single informative clause about what templates are being listed would cost almost nothing and add a great deal.

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 one optional param, no output schema, and read-only annotations, the surface is simple, so the omission is less damaging than it would be for a mutation tool. Still, an agent has no way to know the shape or scope of the returned templates, which leaves the definition incomplete for selection among the many voucher-related siblings.

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?

There is a single optional parameter ('fresh') whose schema description already explains cache-skipping at 100% coverage, so the schema does the work. Per the high-coverage baseline, a 3 applies even though the description contributes no parameter meaning at all.

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 is 'Voucher templates.', a verbatim restatement of the tool name and title, so it conveys no verb, no scope, and no object beyond the name itself. It cannot be distinguished from the sibling 'vouchers' or 'voucher_orders' on the basis of this text.

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 indication of when to call this instead of 'vouchers', 'voucher_orders', or any of the other ~70 siblings. No prerequisites, no exclusions, no alternatives are mentioned.

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