create_note

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

Annotations already communicate that this is a non-read-only, non-destructive mutation. The description adds useful behavioral detail beyond those annotations: the note is attached to a Zotero item and the content can be HTML or plain text. There is no contradiction with the annotations.

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 two tight sentences with no filler. The primary action is front-loaded, and the usage guidance and content-format detail are provided efficiently. Every sentence adds meaningful information.

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 three-parameter create tool with an output schema and safety-relevant annotations already present, the description covers the essential relationship to the parent item and the acceptable content format. It does not describe tags or return behavior, but those are either covered by the schema, output schema, or are minor for this call context.

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 does add semantic value by explaining that parent_key refers to the Zotero item the note is attached to and that content accepts HTML or plain text. However, it does not address the third parameter, tags, leaving that aspect still underdocumented.

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 names a specific verb and resource: 'Create a note attached to a Zotero item.' It further clarifies the intended use ('save reading notes, summaries, or annotations') and distinguishes this from other create actions like create_collection or create_item by specifying that the note is attached to an 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?

The phrase 'Use this to save reading notes, summaries, or annotations on a paper' gives clear usage context. It does not explicitly name alternatives or exclusion criteria, but the attachment-to-item framing makes it easy to distinguish from read-only siblings like get_notes and from attachment-focused tools like attach_pdf.

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