zotero_manage_note

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

No annotations are provided, so the description carries the full disclosure burden. It clearly discloses that append=False REPLACES the whole body (a destructive default), that delete moves to Trash (recoverable), that emptying Trash is manual, and the writable library requirement. It also notes HTML preservation behavior. This is strong behavioral transparency for a mutation tool, though it doesn't describe return value/response format.

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 and information-rich with every sentence earning its place, but it is somewhat long for a single paragraph, making it harder to scan quickly. It's front-loaded with the core purpose and action-specific details, and the inline example is valuable. Slightly longer than ideal but every part contributes meaningfully.

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?

This is a complex parameterized mutation tool with 6 parameters at 0% schema coverage and no annotations. The description compensates fully by explaining every parameter across all three actions, the destructive-replace default, recovery semantics, HTML formatting preservation, prerequisite access requirements, and scope exclusions. The inline example ties parameters together. This is complete for the tool's complexity.

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 fully explain all parameters, and it does. It explains item_key semantics per action (parent key vs. note's own key), note_text formats (plain or simple HTML with a preserved list), note_title as heading, append behavior with default false meaning replace, and optional tags. It even provides a concrete populated example. This exceeds the baseline compensation expected.

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 opens with a clear verb+resource statement: 'Create, update, or trash a Zotero note.' It covers all three actions with clear scope, and explicitly differentiates itself from related tools by noting 'Notes only, not items/collections/attachments.' This distinguishes it well from sibling tools like zotero_delete_item, zotero_create_collection, etc.

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 action-by-action usage: which key to use for create vs. update/delete, what fields each action needs, when append vs. replace applies, and how to use zotero_get_notes(raw_html=True) to preserve formatting. It names the alternate tool (zotero_get_notes) for fetching. It also states the prerequisite requirement of a writable library. This is comprehensive guidance with clear when and when-not.

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