zotero_add_note

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

No annotations are provided, so the description carries the burden of disclosing behavior. It reveals an important behavior: 'Plain text is converted to simple HTML; if you pass HTML it is stored as-is.' It also explains the effect of parent_item_key. While it doesn't cover permissions or reversibility, these are less critical for a note-adding tool, and the provided details are meaningful.

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 concise and well-structured. The one-line purpose is followed by a clean Args list. Every sentence adds value, with no redundancy or filler.

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?

For a simple note-adding tool with an output schema present, the description is complete. It covers purpose, all parameters, and key behavioral details. The presence of an output schema means return values don't need to be described, and the description is sufficient for an agent to select and invoke the tool correctly.

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 fully compensates. The Args section explains all three parameters: text (including HTML conversion), parent_item_key (attach or standalone), and tags (tags for the note). This adds crucial meaning beyond the bare schema property names.

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's function: 'Attach a note to a reference, or create a standalone note.' The verb+resource combination is specific and distinguishes it from sibling tools like zotero_add_tags or zotero_attach_link. It unambiguously indicates the tool is for notes, not other item types.

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 provides clear usage context by explaining the two modes: attach to a reference or create standalone. It also instructs to omit parent_item_key for standalone notes. While it doesn't explicitly name alternative tools, the scope is evident from the sibling list and the description's own wording, making it clear when this tool is appropriate.

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