obsidian_create_note

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

No annotations are provided, so the description bears full responsibility for behavioral disclosure. It implies a write operation but does not specify concurrency behavior, conflict handling, or whether existing files are overwritten. It only states it returns a success message or error, without detail.

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 concise, with a clear one-line summary followed by a structured Args/Returns section. It is front-loaded and every sentence adds value. Slightly verbose for the Args format, but still efficient.

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 tool's complexity (5 parameters, behavioral implications), the description lacks important context such as template details, error handling, and requirements for the vault and path. It does not cover what happens if the note already exists, or how the structured template behaves.

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%, and the description adds brief explanations for each parameter (e.g., 'vault: Name or path of the vault'). This provides basic meaning beyond the bare schema, but lacks examples or format details. It compensates minimally for the lack of schema descriptions.

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 'Create a new note with a structured template,' clearly identifying the action and resource. However, it does not differentiate from sibling tools like obsidian_create_note_in_app or obsidian_write_note, which might have overlapping functionality.

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 guidance is provided on when to use this tool versus alternatives. There is no mention of prerequisites, such as the vault needing to exist, or when to prefer this over create_note_in_app or write_note.

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