edit-note

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

The description mentions that newContent replaces entire content and noteId skips title resolution, but lacks details on authorization, idempotency, or error conditions. With no annotations, the description carries some behavioral context but not comprehensively.

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 with two clauses, no superfluous words. It efficiently conveys the core action and identification method.

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?

With 5 parameters, no output schema, and no annotations, the description is minimal. It fails to address edge cases (e.g., both noteId and title provided), return value, or behavior when no note matches.

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%, so baseline is 3. The description adds some context (e.g., path for disambiguation, newContent replaces entire content) but largely repeats schema information without significant extra meaning.

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 explicitly states the tool edits an existing Apple Note's title and/or content, and identifies the note by noteId or current title. This clearly distinguishes it from sibling tools like create-note or 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 does not provide guidance on when to use this tool versus alternatives such as append-to-note, or when not to use it. No contextual usage hints are given.

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