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

Annotations already declare the safety profile (readOnlyHint=false, idempotentHint=true, destructiveHint=false, openWorldHint=false), so the description need not restate it. However, it adds essentially nothing beyond them: 'privacy-filtered project metadata' is vague and it never explains the concurrency model implied by required expectedVersion, nor what the update does to the existing note.

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?

It is a single short sentence with no padding, which is good, but the sentence is awkwardly worded ('Update hosted update context note') and not clearly front-loaded with the key constraint. Brevity here reflects thinness rather than disciplined editing.

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 mutation tool with a nested details object and required idempotencyKey/expectedVersion, the description says nothing about what fields are updatable, that details is bounded metadata, or how conflicts are resolved. The schema and annotations carry nearly all the load, leaving the description as a near-redundant restatement of the name.

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 the schema itself documents all 7 parameters, including the idempotencyKey and expectedVersion semantics. The description adds no parameter-level meaning beyond the schema, so the baseline of 3 applies.

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 contains a verb ('Update') and resource ('context note'), so the basic action is inferable, but the phrasing 'Update hosted update context note using privacy-filtered project metadata' is garbled and self-referential ('update ... update'). It gives no differentiation from close siblings such as move_context_note, convert_context_note, archive_context_note, or delete_context_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?

There is no statement of when to use this tool versus alternatives, no prerequisites, and no mention of the related note-mutation siblings. 'using privacy-filtered project metadata' hints at an input constraint but not at usage context.

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