obsidian_prepend_note

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

No annotations exist, and the description only states it prepends content. It fails to disclose behaviors like what happens if the note does not exist, if content is empty, or any authorization or side effects of this mutation operation.

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 relatively short but includes redundant sections like 'Args:' and 'Returns:' that are already covered by the input schema and output schema. It could be more concise by removing these repeated structures.

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 3 required parameters, no annotations, and an output schema only mentioned as 'Success message or error,' the description lacks important context such as error handling, constraints on content, or vault path validation. It feels incomplete for a mutation tool.

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 0%, so the description must compensate. It provides brief meanings ('Name or path of the vault,' 'Path to the note within the vault,' 'Content to prepend') that add some value beyond the parameter names, but they remain somewhat vague and do not specify format or constraints thoroughly.

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 'Prepend content to the beginning of an existing note,' which is a specific verb-resource combination. It naturally distinguishes from sibling tools like obsidian_append_note and obsidian_write_note.

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 no guidance on when to use this tool versus alternatives. It does not mention prerequisites, exclusions, or scenarios where other tools (e.g., obsidian_append_note) would be more appropriate.

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