stat_voucher

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

With no annotations, the description carries the full burden. It states the operation is a list, implying read-only and non-destructive behavior, and mentions the optional filter. However, it does not disclose any additional behavioral traits such as result ordering, pagination, or potential side effects, which is acceptable for a simple read operation.

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?

The description is a single, front-loaded sentence with no unnecessary words. It clearly communicates the action and the optional filter without elaboration.

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 tool with one optional parameter and an output schema, the description is sufficient to understand its purpose and usage. No edge cases are apparent from the schema, and the inherently safe nature of a list operation reduces the need for extensive behavioral notes.

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?

The schema already provides a complete description of the only parameter (create_time) with 100% coverage, so the description's mention of optional filtering adds little new meaning. It correctly restates the optionality but does not go beyond what the schema offers.

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 uses a specific verb ('List') and resource ('hotspot vouchers'), clearly stating the tool's function. The optional filter by creation time adds specificity, and no sibling tool overlaps with voucher listing, so it is well differentiated.

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?

The context is clear: this is the tool for listing hotspot vouchers, with an optional creation time filter. No alternatives or exclusions are mentioned, but since there are no overlapping sibling tools, explicit comparison is unnecessary.

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