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

Annotations declare readOnlyHint=false, destructiveHint=true, openWorldHint=false; the description adds real context beyond them — the confirmation policy, that the write is limited to the caller's own record, and that the change is undoable from the same surface, which reconciles a destructive-hint tool with immediate execution. It leaves one meaningful behavior undisclosed: whether omitted fields are preserved or cleared (patch vs. replace semantics).

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?

Front-loaded with the action and the field list, then the confirmation policy. The system-policy sentence ('Everything destructive, outbound or financial still proposes and waits') is a bit of boilerplate but does usefully bound the exception this tool represents.

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 6-parameter mutation with no output schema, the description covers scope, execution/confirmation behavior, and undoability. Missing only the update-semantics detail (partial vs. full replacement) that would let an agent predict exactly what changes.

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 description coverage is 0%, so the description must carry the semantic load; it does list the five mutable field names, but that largely restates the schema's property names. It never mentions note_id (the required parameter) or the accepted string-or-integer ID form, so low-coverage parameters remain unexplained.

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?

States a specific verb and resource (update fields of a personal note) plus the exact editable fields (title, body, folder, pinned, tags), and scopes it to 'one of the caller's personal notes'. An agent can distinguish it from create_note, get_note, and delete_note without opening any schema.

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?

Implicitly clear on when to use it — mutating existing fields of an owned note — and explicit about the execution model (runs immediately, no plan_token, undo available). It does not name the alternative for creating a note or for notes owned by others, but the scope statement ('Only the caller's own note is reachable') tells the agent when not to bother.

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