zotero_update_note

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

Discloses all key behaviors: append=False replaces content (destructive), append=True concatenates, requires writable library, fails in local-only mode, and clarifies item_key is the note's own key.

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?

Concise yet comprehensive; every sentence is purposeful and well-structured, starting with the action, then key clarifications, parameter details, usage tip, requirement, and example.

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?

Fully covers all aspects needed for correct usage: item key specificity, append mode, formatting preservation, authorization requirement, and provides an example. Sibling tools list provides context.

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 coverage is 100%, and the description adds significant value beyond the schema: explains item_key meaning, append effect, and formatting preservation, plus an example.

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 clearly states the tool updates the HTML body of an existing Zotero note, distinguishing it from sibling tools like zotero_create_note and zotero_get_notes.

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?

Provides explicit guidance: how to obtain the correct item_key using zotero_get_notes or zotero_search_notes, explains append behavior, advises on preserving formatting, mentions library requirements, and includes an example.

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