Vault

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

The description mentions 'whole-file writes' for create/update/delete, providing some behavioral context. Since no annotations are provided, more detail on auth, rate limits, or side effects would be needed for a higher score.

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?

Two sentences, no fluff. The first sentence states the purpose, the second enumerates actions with brief comments. It is concise but could be better structured with bullet points.

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?

Given the complexity (6 parameters, multiple actions) and lack of output schema/annotations, the description does not cover return values, errors, or permissions. It references an external overview doc, but is not self-contained.

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 description adds meaning to the action parameter by specifying each action's purpose (e.g., 'list (browse notes)', 'create_from_template (scaffold from template)'). This adds value beyond the schema descriptions for parameters.

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 it manages vault notes and lists all actions. It distinguishes the vault as a general markdown notes vault, but does not explicitly differentiate from sibling tools like 'view' or 'edit'.

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?

No explicit guidance on when to use this tool versus alternatives. It only hints at reading a separate overview document for search strategy and conventions.

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