list_customer_vault

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

With no annotations provided, the description must carry the behavioral disclosure burden. It mentions 'Read-only' and optional date-range filtering, which are useful, but it does not disclose pagination, return format, permissions, or limitations. There is no contradiction with annotations, but the disclosure is minimal.

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 sentence, front-loaded with the action and resource. It is concise, but the parenthetical 'report_type=customer_vault' introduces a technical detail that is not explained and may be unnecessary for the agent.

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 simple with three optional parameters and no output schema, so the description should explain what the tool returns. It covers purpose and filtering options but does not describe the response shape or any caveats, leaving the agent to infer the return format from the tool name.

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 input schema has 100% coverage for parameter descriptions, so the baseline is met. The description adds a general statement about optional filtering, but it does not provide additional semantic detail beyond what is already in the schema descriptions.

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 that this tool lists stored Customer Vault records, with an optional date-range filter. This distinguishes it from sibling tools like get_customer_vault_record, which retrieves a single record, by focusing on the list action.

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 description provides clear context that this is for listing records with optional filtering, but it does not explicitly state when to use this tool versus alternatives such as get_customer_vault_record or search_transactions. Usage is implied rather than explicitly directed.

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