Zotero Manage Note

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

No annotations are present, so the description carries the full behavioral burden, and it delivers: Markdown is NOT supported and stored literally, append=True vs False behavior is explained, delete goes to Trash and is recoverable, and local-write or API-key prerequisites are stated. This goes well beyond the schema.

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?

Dense and well organized: action summary, key semantics, per-action rules, exclusions, prerequisites, then a concrete example. Although long, each sentence adds necessary information and the most important scoping comes first.

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?

Complete for all three actions, with formatting caveats, key sourcing, recovery semantics, and an example. The only minor gap is that note_title/tags are described as create-time behaviors, so it is not fully explicit whether they can be changed during update.

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%, but the description compensates by defining the overloaded item_key semantics per action, which parameters each action needs, the plain/HTML note_text format, append's interaction with body replacement, note_title as heading, and tags being optional. Every parameter is given operational meaning.

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?

Opens with a specific verb+resource: 'Create, update, or trash a Zotero note.' It also distinguishes itself from siblings with 'Notes only, not items/collections/attachments,' so an agent won't confuse it with zotero_update_item or zotero_delete_item.

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 clear context: how to obtain the correct item_key via zotero_get_notes, that a writable library is required, and that note-level operations are in scope while items/collections/attachments are excluded. It doesn't explicitly name the alternative tool for non-note entities, but the exclusion is clear enough.

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