contacts_update_note

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

Annotations already indicate readOnlyHint=false (mutation), destructiveHint=false (not destructive), and idempotentHint=true. The description 'Update Note' adds no additional behavioral context such as side effects, required permissions, or response details. It neither contradicts annotations nor enriches them.

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 extremely concise (two words), which is good for length, but it is under-specified. It does not provide enough context, so the conciseness detracts from usefulness. It is not wordy, but it does not 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?

With 7 parameters and no output schema, the description is completely inadequate. It does not explain what the note is, which fields can be updated, or what the return value looks like. An agent cannot confidently call this tool without additional external knowledge.

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 only 29% (only id and contactId have descriptions). The description does not clarify any of the other five parameters (body, color, title, pinned, userId). It adds zero value beyond the schema, which itself is incomplete. The agent is left guessing what fields are updatable.

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 'Update Note' clearly names the action (update) and resource (note), so an agent knows it modifies a note. However, it does not differentiate from sibling tools like contacts_create_note or contacts_delete_note, though the verb and resource are specific enough to avoid ambiguity.

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 guidance on when to use this tool versus any alternative. It does not mention prerequisites, conditions, or when a create/get/delete note would be more appropriate. No context is provided.

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