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

Annotations are empty, so the description carries the full burden for behavioral disclosure. It implies a read-only 'Lists' operation but does not explicitly state that, nor does it mention pagination, limits, or any side effects. The only behavioral additive is the scoping note about vouchers being issued by any account_fk in this wallet, which is more semantic than behavioral.

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 first sentence is repeated verbatim, which is redundant and wastes space. The @param block is structured and readable, but the duplication and the relatively verbose param explanations could be tightened. The description is not concise, but the formatting makes it scannable.

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?

The tool is a simple list operation with an output schema, so return values are covered elsewhere. However, the description fails to provide any context about when this tool is appropriate relative to the many sibling tools. It does not mention filtering, sorting, or the relationship to other voucher-related tools, leaving the agent without enough information to choose it confidently among alternatives.

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 0%, so the description's @param lines are essential. They provide meaning for api_key, token, and wallet_fk, explaining where they come from (e.g., 'wallet_api_token provided by /access/login'). However, the explanations are somewhat generic and do not deeply clarify the semantic role of each parameter in this specific operation, such as what wallet_fk represents in the vault context.

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 clearly states the tool's purpose: 'Lists all vouchers kept in this wallet's vault.' This is a specific verb+resource combination that distinguishes it from sibling tools like wallet_accounts_list or wallet_card_list, which list other entity types. The additional clarification that these are 'vouchers issued by any account_fk in this wallet' further sharpens the scope.

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?

No guidance is given on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or alternative tools such as netfluid_voucher_check. The only context is the @param lines, which explain authentication but not usage scenarios.

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