Vault List

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered. The description adds the meaningful operational fact that this is an internal SPA-invoked tool, but says nothing about recursion depth, whether hidden files are included, or pagination behavior on large vaults.

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?

Three short lines, front-loaded with the actual capability before the invocation context. Nothing is padded, though the 'Not visible to the LLM' line is somewhat redundant with '(app-only)'.

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?

With an output schema, complete annotations, and a fully documented single parameter, the structured data carries most of the burden. The description is adequate but leaves the main ambiguity unresolved: how this differs from the several other listing tools in the sibling set.

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% and the single `folder` parameter is already documented as 'Folder to list (root if omitted).' The description adds no syntax, path format, or delimiter conventions beyond that, so the baseline of 3 applies.

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?

States a concrete verb and resource: lists folders and notes within a vault directory. It partially distinguishes itself from list_documents and list_folders by covering both in one call, though it never names those siblings explicitly.

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 '(app-only)' marker plus 'Called by the SPA browser view' establishes who invokes it, which is a usage constraint rather than routing guidance. It gives no when-to-use versus list_documents, list_folders, or browse_vault, so an agent must infer selection from names alone.

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