create_note

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

With no annotations, the description encodes key behaviors: automatic parent folder creation and failure on existing note unless overwrite is true. This provides sufficient transparency for a simple file creation tool, though authorization or rate limits are not discussed.

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 sentences, front-loading the purpose and adding critical behavior details without any 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 simplicity of the tool and complete schema coverage, the description covers the key creation behavior. It does not specify return value, but for a create operation this is often implied.

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%, and the description adds value by explaining that parent folders are created automatically (path) and that the operation fails if the note exists unless overwrite is true (overwrite). This goes beyond the schema descriptions.

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 tool creates a new markdown note. It distinguishes from siblings like edit_note and append_note by emphasizing creation of a new note with automatic folder creation and existence check.

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 provides clear context on when to use (creating a new note) and the behavior when a note already exists. It does not explicitly mention alternatives, but sibling tool names are available for reference.

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