create_note

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

With no annotations provided, the description carries the full burden and does substantial work: it discloses the creation action, the failure mode when the note exists, the overwrite escape hatch, and automatic creation of intermediate subfolders. These are non-obvious behaviors beyond what the tool name alone conveys.

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?

Three short sentences with no filler. The core action comes first, followed by the failure condition and the subfolder behavior. Every sentence adds useful operational detail.

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?

Covers the action, failure condition, overwrite behavior, and subfolder creation, which is nearly complete for a straightforward create tool. The main gap is the lack of return/response information, but since there is no output schema, the description is otherwise sufficient.

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 coverage is 100%, so the baseline is 3, but the description adds meaning beyond the schema: it explains that the path parameter can include intermediate subfolders that will be created if needed, and it clarifies the practical effect of 'overwrite=true' on the failure behavior. This compensates above 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?

States a specific action ('Creates a new note') and resource ('in the vault'), and its semantics are clearly distinct from sibling tools like read_note, append_to_note, and delete_note. The phrase 'Fails if the note already exists, unless overwrite=true' reinforces that this is a create-not-update operation.

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 gives clear mechanics (creation, overwrite behavior, subfolders) but no guidance on when to choose this tool versus alternatives such as append_to_note for existing notes or search_note for discovery. There is no explicit 'use when' / 'use instead' guidance.

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