notes_update

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

Discloses key behaviors: partial update semantics, tag replacement, stability of slug/id. Annotations indicate destructive and idempotent; description aligns and adds context. No contradiction.

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 concise sentences, front-loaded with main action, no fluff. Efficiently conveys the essential behavior.

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?

Adequately covers update behavior for a tool with no output schema. Could mention return value (e.g., updated note), but not critical given common patterns.

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% with param descriptions, but the description adds value by explaining partial update ('omitted fields untouched') and tag replacement, which goes beyond schema min/max.

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 tool's purpose: updating a note's fields by id. It lists the updatable fields and distinguishes from other operations like create, delete, read by implying an existing note is modified.

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?

Provides guidance on partial updates ('Omitted fields are untouched') and tags behavior ('tags replace all'), but does not explicitly contrast with sibling tools like notes_create or notes_append for when to use this vs others.

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