Save a new note with a title, optional body, and tags for later search and organization.
Save a new note with a title, an optional body and optional tags.
| Name | Required | Description | Default |
|---|---|---|---|
| body | No | Note text. | |
| tags | No | Tags, lowercased automatically, a leading # is stripped. | |
| title | Yes | Short title, required. |
Changes observed during successful MCP inspections.
v1.0.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions that body and tags are optional, but it does not disclose mutation side effects, return behavior, or failure modes. Tag normalization is mentioned only in the schema, not in the description.
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?
One sentence with no filler, front-loading the core action ('Save') and then listing the optional parameters. Every word contributes to understanding.
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?
For a simple three-parameter creation tool, the schema covers all parameters well, but the description lacks usage guidance and behavioral context. With no annotations and no output schema, an agent gets only the bare minimum needed to invoke the 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 100%, so the schema already documents title, body, and tags. The description adds marginal framing by identifying body and tags as optional, but it does not meaningfully expand on the schema's parameter details.
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 verb 'Save' and the resource 'a new note', which distinguishes creation from the sibling operations search_notes, list_notes, get_note, update_note, and delete_note. It also signals the operation is for creating, not modifying or retrieving.
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 word 'new' implies this tool is for creating rather than updating, but the description does not explicitly say when to use it over update_note or how it relates to the other sibling tools. Usage context is implied rather than stated.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.