Create Note

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

Annotations already declare readOnlyHint=false, indicating this is a write operation. The description adds no further behavioral context, such as whether the note is created in a default folder, any auth requirements, or side effects. It neither contradicts nor enriches the annotation-provided safety profile.

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 a single sentence, 'Creates a new note', which is maximally concise and front-loaded. It contains no filler words or redundant clauses, making it an efficiently sized statement of purpose.

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?

The tool is simple, and the schema fully documents all parameters with descriptions. Annotations convey the write-safety profile. However, the description lacks usage guidance or any mention of behavior beyond the bare action, making it minimally viable but not complete from an agent-facing perspective.

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?

All three parameters (body, title, folderName) have descriptions in the input schema, achieving 100% schema description coverage. The description itself provides no parameter-level details, so it leans entirely on the schema, earning the baseline 3 for high coverage.

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 uses a specific verb 'Creates' and identifies the resource 'note', clearly distinguishing it from sibling tools like search-notes, list-notes, and read-note. There is no ambiguity about what action is performed on what entity.

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 no guidance on when to use this tool versus alternatives. It does not mention any context, exclusions, or alternative tools. The single sentence merely states the action without any situational advice.

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