create_note

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

No annotations are provided, so the description must carry the behavioral transparency burden. It discloses the key behavioral traits: automatic parent folder creation, optional frontmatter, and the overwrite/failure policy. It does not mention return values or error details, but for a create-note operation the main side effects are well covered.

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 two concise sentences with no filler. The primary action is front-loaded, and the edge cases (parent folders, failure-if-exists) are included efficiently.

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 100% schema coverage and no annotations or output schema, the description covers the essential elements: what the tool does, auto-created parent folders, and the overwrite behavior. It could mention the return value, but for this simple create operation the description is adequate for an agent to invoke it 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?

Schema description coverage is 100%, and the schema already explains path, content, overwrite, and frontmatter in detail. The description adds little beyond restating frontmatter and overwrite behavior, so it does not meaningfully enhance the parameter semantics.

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 action: 'Create a new note in the vault' with optional YAML frontmatter. It also distinguishes this from siblings by emphasizing 'new' and the failure-if-exists behavior, which is different from update_note or delete_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?

It gives clear context for when to use this tool: to create a new note, with parent folders created automatically, and it fails if the note already exists unless overwrite=true. It does not explicitly recommend update_note as an alternative for existing notes, so it falls short of fully explicit when/when-not guidance.

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