Create Note

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

Annotations are minimal (readOnlyHint=false, etc.), so description carries the burden. It discloses key behaviors: fails if exists (safety), creates directories automatically, appends .md if omitted. No contradiction with annotations.

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?

Four sentences, each providing essential information without redundancy. The main action is front-loaded. No wasted words.

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 simplicity (3 parameters, no output schema, clear annotations), the description covers all needed context: creation behavior, error handling, directory creation, extension handling. Completeness is achieved.

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% with descriptions, but description adds meaning beyond schema: path gets .md appended, frontmatter is JSON string rendered as YAML, content is markdown body. These enrich parameter understanding.

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 'Create a new markdown note at the given path with body content and optional YAML frontmatter,' specifying a specific verb and resource. It distinguishes from siblings by noting failure if the note already exists and pointing to alternatives (append_to_note, etc.).

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?

Explicitly tells when to use this tool (new notes) and when not to (existing notes), with named alternatives (append_to_note, prepend_to_note, update_frontmatter). Also explains automatic directory creation and .md extension.

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