zotero_create_note

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

With no annotations, the description carries the full burden. It discloses that the note becomes a child item, that HTML preservation is limited to specific tags, and that the tool fails in local-only mode. It does not describe side effects or return schema, but output schema exists, so that is acceptable.

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 a single well-organized paragraph that front-loads the core action, then systematically describes each parameter, includes a usage constraint, and ends with an example. No wasted words.

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?

Given the tool has 4 parameters, no annotations, an output schema, and many siblings, the description covers all needed aspects: purpose, parameters with examples, usage constraints, and differentiation from similar tools.

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?

The description adds significant meaning beyond the schema: it clarifies 'item_key' as parent key, details allowed HTML tags for 'note_text', and specifies 'tags' as optional strings. Schema coverage is 100%, so baseline is 3, but the extra details raise it to 4.

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 creates a new child note attached to a Zotero item, using specific verbs and nouns. It distinguishes from sibling tools like zotero_update_note by mentioning editing as an alternative.

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 explicitly tells when to use this tool versus alternatives (zotero_update_note for editing) and includes a constraint about writable library mode. However, it does not fully elaborate on when not to use it beyond the mode restriction.

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