Vault

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

No annotations are provided, and the description does not disclose behavioral traits beyond listing actions. It fails to mention idempotency, side effects (e.g., destructive deletes), permissions required, or error handling behavior. For a mutation tool, this is insufficient.

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 sentence that efficiently lists the tool's capabilities and target file type. It is front-loaded with key information, though it could benefit from a slight structure to separate action types.

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 of 6 parameters and multiple actions with no output schema, the description is too sparse. It omits critical details like how paths are resolved, content format expectations, and the difference between create and create_from_template, leaving the agent to infer from the schema alone.

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?

With schema coverage at 33% and 6 parameters, the description adds no extra meaning beyond what the schema already provides. It does not explain how to use the action parameter or map it to the desired operation, nor does it clarify the relationship between path, directory, content, and template 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 the tool manages vault notes with a specific list of actions (list, read, create, update, delete, stat, create_from_template) and operates on .md files. This distinguishes it from sibling tools like edit, system, view, workflow which handle different functionalities.

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?

There is no guidance on when to use this tool versus alternatives, nor any preconditions or context cues. While the actions are listed, the description does not explain prerequisites, such as the need for an existing path or directory, or when to avoid certain actions.

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