list_items

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

Given no annotations, the description carries the full burden but only discloses the scope behavior (omit vault_id). It doesn't mention return format, ordering, or potential large result sets, but the read-only nature is implied by 'list'.

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?

Single sentence, front-loaded with action, no fluff. Every word earns its place.

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 simple list tool with one optional parameter and no output schema, the description sufficiently communicates its function and the key optional behavior. However, it doesn't clarify what types of items are returned or any pagination, but these are not critical given the tool's simplicity.

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 covers vault_id 100% with 'Vault share ID (optional)', but the description adds meaning by explicitly stating the effect of omitting it (lists across all vaults). This clarifies user intent beyond the schema.

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 ('items'), and clearly defines the scope via optional vault_id. It distinguishes from sibling list_vaults by focusing on items rather than vaults.

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?

Provides clear context that omitting vault_id lists across all vaults, implying when to use the optional parameter. However, it doesn't explicitly mention alternatives or when not to use this tool (e.g., for viewing a single item's details).

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