Create a new note in Apple Notes from supplied text, using the first line as the title. Use it when an agent needs to save content directly to Notes.
Create a new note in Apple Notes with the given text. (risk: mutating)
| Name | Required | Description | Default |
|---|---|---|---|
| body | Yes | The note's content. The first line becomes its title. |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
With no annotations, the description carries the full behavioral burden. The '(risk: mutating)' tag usefully flags a write operation, but nothing is said about target account/folder, permissions, reversibility, or what happens on failure.
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?
Two compact clauses, front-loaded with the action and ending with a useful risk tag. Nothing is redundant or padded.
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 one-parameter create tool the description is minimally sufficient, and the schema covers the parameter fully. It omits destination details (account/folder) and post-creation behavior, which matter for a mutation with no annotation coverage.
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 single 'body' parameter is fully documented there, including the title-from-first-line behavior. The phrase 'with the given text' merely restates the schema, so the baseline 3 is correct.
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 states a clear verb and resource: 'Create a new note in Apple Notes', which cleanly separates it from the read-oriented sibling notes_read_open_note. It stops short of explicitly naming alternatives, but the action is unambiguous.
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?
There is no when-to-use or when-not-to-use guidance. An agent gets no signal about when creating a note is the right call versus the read sibling, nor any prerequisite context such as which account or folder receives the note.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.