list_vault

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

With no annotations, the description carries the full burden of behavioral disclosure. It indicates a read-only 'List' operation but does not mention pagination behavior, default limit, ordering, or whether the result is a flat array. The default for limit is only in the schema, not in the description. Minimal behavioral context is provided.

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, well-structured sentence. It front-loads the action ('List'), specifies the resource ('bookmarks in your Vault'), and adds one optional modifier. There is zero filler or repetitive content.

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 tool with two optional parameters and no output schema, the description is minimally adequate. It states the purpose and filtering capability, and the schema covers parameter details. However, without output schema or annotations, there is no information about the return format, ordering, or pagination behavior, leaving some gaps for the agent.

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 100%, so the baseline is 3. The description adds no meaning beyond the schema: 'optionally filtered by category' is already in the category parameter's description. Neither parameter gains additional context from the description.

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 lists bookmarks in the Vault, with an optional category filter. This distinguishes it from sibling tools like search_vault (search) and list_sparks (sparks). The verb 'List' is specific and the resource is well-defined.

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 no guidance on when to use this tool versus alternatives like search_vault. It does not mention any exclusions, prerequisites, or scenarios where another tool would be more appropriate. The usage context is only implied by the tool's purpose.

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