create_note

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

The description discloses a key behavioral trait beyond the schema: it automatically derives the title from the first H1 heading. It also clarifies that content is in markdown format. With no annotations available, this adds necessary transparency about how the tool processes input, though it doesn't cover edge cases like missing H1 or output behavior.

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 only three sentences, front-loading the core purpose and then providing the necessary detail about title extraction. It avoids redundancy and stays tightly focused on the essential information for correct use.

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 one-parameter create tool, the description covers the primary purpose and the most critical behavior (title extraction). The presence of an output schema covers return values. However, it doesn't mention what happens if the content lacks an H1 heading or other edge cases, which could be relevant for the agent.

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?

The schema provides only a string property named 'content' with no description (0% coverage). The description explains that content is markdown and should start with '# Title', adding essential semantic meaning that the schema lacks. This fully compensates for the schema's lack of parameter documentation.

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 note with markdown content,' giving a specific verb, resource, and content format. This distinguishes it from sibling tools like list_notes, get_note, update_note, and 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?

The description provides an implicit usage context (when creating a new note) and adds an important operational guideline: the title is automatically extracted from the first H1 heading, so content should start with '# Title'. While it doesn't explicitly name alternative tools, the guidance prevents misuse and clarifies the expected content structure.

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