evernote_update_note

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

No annotations are provided, so the description carries the full behavioral disclosure burden. It states that the note is updated, but it does not describe required permissions, whether changes are destructive or reversible, how the target note is identified, or what side effects occur.

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 a single front-loaded sentence with no filler. It states the essential operation and fields without unnecessary detail.

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 no annotations, no output schema, and an empty input schema, the description is too thin. It omits how to identify the target note, what parameters are required, and what the update operation does beyond the basic purpose.

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?

The input schema has zero parameters, which gives a baseline of 4. The description adds semantic context that the updatable fields are title and content, though it does not specify how the existing note should be selected because the schema provides no parameters.

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 clear verb and resource: it updates the title or content of an existing Evernote note. This distinguishes it from evernote_create_note and evernote_read_note, but it does not explicitly differentiate from the sibling update_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?

The word 'existing' implies this is for editing existing notes rather than creating new ones, but there is no explicit guidance on when to choose this tool over alternatives such as evernote_create_note or update_note. Prerequisites and note-selection requirements are also absent.

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