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

Annotations already declare this is a non-destructive, idempotent, closed-world mutation, so the safety profile is covered. The description adds only the phrase 'privacy-filtered project metadata', which is vague and does not disclose what archiving does to the note, whether it is reversible, or how version conflicts are handled — all relevant for a mutation with an expectedVersion guard.

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?

A single short sentence with no filler, which is structurally clean. However, its brevity comes at the cost of under-specification rather than efficient communication, so it does not fully earn its place.

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?

This is a 7-parameter mutation with a nested object, an idempotency key, an expectedVersion concurrency guard, and no output schema. For that complexity the description is far too thin — it says nothing about what archiving changes, conflict behavior, or retry semantics that the agent must reason about.

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 100%, so every parameter already carries its own guidance, and the baseline is therefore 3. The description's 'privacy-filtered project metadata' loosely gestures at the bounded details object but adds no syntax or constraint information beyond what the schema states.

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 gives a verb ('Update') and a resource ('hosted archive context note'), but it is ambiguous whether the tool archives a note or edits a note that lives in an archive, and the word 'Update' conflicts with the 'archive_' prefix in the name. With siblings like update_context_note, delete_context_note, move_context_note and convert_context_note, the description does nothing to distinguish this tool from them.

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 statement of when to use this tool versus update_context_note or delete_context_note, and no prerequisites or exclusions are given. 'using privacy-filtered project metadata' hints at a constraint but does not tell the agent when this operation is the right choice.

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