vault_move

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It transparently states the automatic wikilink update side effect, the exact-path requirement, and the markdown link output format. It does not detail error conditions or reversibility, but covers the most impactful behaviors.

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 tightly written, with each sentence serving a distinct purpose: the action, the side effect, the path constraint, and the output format usage. It wastes no words and front-loads the primary function.

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 there is no output schema, the description effectively explains the output shape (markdown links) and the side effect of link updating. It does not cover error scenarios (e.g., missing old_path) or the return value for a successful move, but overall it provides sufficient context for an agent to use the tool correctly.

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 schema covers all three parameters (100% coverage), so the baseline is 3. The description adds value by reinforcing the exactness of both paths and providing crucial guidance on how to interpret and pass path values (using only the bracket text, not the full markdown link) to other tools.

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's function: 'Move or rename a markdown file within the vault.' It also specifies the key side effect of automatically updating wikilinks, which distinguishes it from sibling tools like vault_write or vault_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?

The description provides clear operational context: paths must be exact, and it explains how to handle the output path format when passing paths to other vault tools. However, it does not explicitly mention when to use this tool instead of alternatives or provide exclusion criteria.

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