get_user_vaults

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

No annotations present, so description relies solely on itself. It indicates a read-only operation (list), but lacks details on pagination, rate limits, or what 'configured wallet' means. Adequate but basic.

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, efficient sentence with no filler. Front-loaded and to the point. 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?

No output schema; description does not explain return format or error conditions. For a simple list tool, it is partially complete but could specify that result is an array of vault IDs.

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?

Adds context beyond schema: clarifies that 'address' is optional and defaults to configured wallet. Schema already describes parameters well (100% coverage), so description adds marginal but helpful value.

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?

Description clearly states 'List all vault IDs', a specific verb-resource pair. It distinguishes from sibling tools like get_vault_summary and close_vault by focusing on listing IDs for a wallet.

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?

Implies usage for listing vaults of a wallet, but no explicit when-to-use, alternatives, or exclusions provided. Minimal guidance beyond the obvious.

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