obsidian_move

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

No annotations are provided, so the description must disclose behavior. It covers key behaviors: moving vs renaming, selection by file or path, and the requirement that one of file/path be provided. However, it does not disclose overwrite behavior or return values.

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 well-structured with a concise summary, parameter explanations, and examples. It is appropriately sized for the tool's complexity, though the 'One of file or path is required' line is slightly redundant with the parameter descriptions.

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?

The tool has no output schema and no annotations, so the description is the primary source of context. It covers purpose, parameters, and examples, but lacks information about return values, error conditions, or overwrite behavior. For a file-moving tool, this is a moderate gap.

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 input schema provides full descriptions for all 3 parameters, giving baseline coverage. The description adds clarity on how to choose between file and path, and what the 'to' parameter represents, including the renaming case. This exceeds the baseline.

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 states 'Move or rename a note, selecting it by file name or exact path.' This is a specific verb with a clear resource and scope. It distinguishes from other tools by specifying the selection method, though it does not explicitly differentiate from the sibling obsidian_rename.

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 explains how to invoke the tool and gives examples, but it does not provide guidance on when to use this tool versus alternatives like obsidian_rename. It implies usage through examples but lacks explicit exclusions.

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