zotero_manage_note

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

With no annotations, the description carries full responsibility. It discloses append behavior (replace vs concatenate), trash recoverability, HTML support, and the fact that notes are the only supported resource. It also notes the writable-library requirement. This is comprehensive behavioral disclosure.

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 dense but every sentence contributes: it opens with the core actions, then systematically details each parameter and action-specific behavior, and ends with an example. No fluff or repetition; information is well organized.

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?

The description covers all necessary context for correct invocation: required parameters, per-action semantics, formatting preservation, library permissions, and a concrete example. With an output schema present, not explaining return values is acceptable. The tool is fully self-sufficient.

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 0%, so the description must explain all parameters. It does so thoroughly: action semantics, item_key distinction per action, note_text HTML rules, note_title as heading, tags optional, and append behavior. The example further clarifies parameter usage.

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 explicitly states the tool creates, updates, or deletes (trashes) a Zotero note, and clearly distinguishes it from item/collection/attachment operations. It also names the sibling zotero_get_notes for locating keys, providing clear differentiation.

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 description gives explicit when-to-use guidance per action (create, update, delete), clarifies which item_key applies to each, and instructs how to preserve formatting via zotero_get_notes(raw_html=True). It also notes the requirement for a writable library, effectively stating prerequisites and alternatives.

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