Create Obsidian Note

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

With no annotations, the description carries the full burden and says nothing about the behaviors that matter for a write tool: whether an existing file is overwritten or an error is returned, whether parent folders are auto-created, and where in the vault the note lands. 'Create a new note' is the minimum possible disclosure for a mutation with side effects.

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?

A single seven-word sentence with zero filler and the action front-loaded. The terseness is a completeness problem rather than a structure problem, so it is not penalized twice here.

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?

This is a mutation tool with no annotations, no output schema, and a nested frontmatter object, yet the description covers only the bare action. An agent cannot tell what path or vault location the note is written to, what happens on filename collision, or what a successful call returns.

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 100%, with all three parameters (filename, content, frontmatter) documented including an example filename format and the optional nested frontmatter object. The description adds no meaning beyond that, so the baseline 3 applies.

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 a specific verb and resource ('Create a new note') plus what it carries ('specified content'), so the basic action is unambiguous. It does not distinguish itself from obsidian-update-note, which is the key ambiguity for an agent deciding whether writing to an existing name is a create or an update.

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 versus obsidian-update-note or obsidian-create-folder, and no prerequisites or exclusions. The only implied usage is the obvious 'you want a new note', which the agent could already infer from the name.

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