Update Note

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

Annotations already convey readOnlyHint=false and destructiveHint=false. The description adds the overwrite semantics ('Replace the content') and the library-targeting behavior, which are useful. No contradiction exists between the description and annotations. It doesn't disclose what happens to prior content or the response shape, but with annotations present, a 3 is appropriate.

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?

Two tight sentences with zero filler. The core purpose is front-loaded in the first sentence, and the second delivers the only needed parameter guidance. Every word earns 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?

The output schema exists, so return format needs no explanation. The library-targeting parameters are covered, but with 0% schema coverage the two required parameters rely entirely on self-explanatory naming. For a straightforward replace operation this is adequate but not comprehensive.

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 compensate. It successfully explains library_id/library_type pairing for targeting another library, but says nothing about the two required parameters (note_key, note). These are somewhat self-evident from their names, yet the description leaves them undocumented at zero schema coverage, so full compensation is not achieved.

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 states a specific verb and resource: 'Replace the content of an existing Zotero note.' This clearly establishes a mutation operation distinct from add_note (creation) and delete_note (removal). However, it doesn't explicitly name or differentiate from siblings, so it stays at 4 rather than 5.

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 offers clear parameter-level context ('Pass both library_id and library_type to target another library; omit both to use the configured default'), which is helpful for invocation. But it gives no guidance on when to use this tool versus the many sibling alternatives (add_note, delete_note, update_item_metadata), so the tool-selection guidance is absent.

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