update_note

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

No annotations are provided, so the description carries full burden for behavioral disclosure. It states 'Update an existing note' but does not clarify whether updates are merging or overwriting, what happens to unspecified fields, or if there are side effects or authorization requirements.

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 very concise, containing only one line of text plus a bulleted list of parameters. No unnecessary words, but it could be slightly more structured (e.g., separating purpose from parameter details) without adding length.

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 lack of annotations and output schema, the description is incomplete. It does not explain return values (e.g., success/error), behavior when the note does not exist, or how partial updates are applied. Sibling tools suggest actions like get_note and delete_note, but no cross-referencing.

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 description lists parameters with brief explanations (e.g., 'path: Path to the note'), which adds basic meaning beyond the schema's raw type names. However, with 0% schema description coverage, the description could provide more detail, such as what 'metadata updates' entails (e.g., key-value pairs).

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 verb 'Update' and the resource 'note', which distinguishes it from siblings like create_note and delete_note. However, it lacks specificity about what aspects of the note can be updated (e.g., content, metadata) beyond listing parameters.

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?

No guidance is provided on when to use this tool versus alternatives (e.g., create_note for new notes, delete_note for removal). The description does not mention prerequisites, such as the note existing, or cases where partial updates are preferred.

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