zotero_create_note

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

Without annotations, the description reveals that content is auto-converted to HTML and line breaks preserved, a helpful behavioral detail. However, it does not disclose other aspects like idempotency, error handling, or rate limits.

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?

Two sentences efficiently convey purpose, features, and usage context. 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?

Complete enough for a note creation tool: purpose, use cases, attachment, format handling. Output schema exists, so lack of return value explanation is acceptable. Minor gap: no mention of error conditions.

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 meaning for 'content' (HTML conversion, line breaks) and 'parent_key' (attach to paper), but 'tags' is not mentioned. With 0% schema description coverage, the description partially compensates but misses one parameter.

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 note in Zotero with formatting support, distinguishing it from sibling tools which are all get/search operations.

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?

Explicitly lists use cases (literature reviews, summaries, research memos) and explains when to use parent_key for attachment, but does not mention when not to use or alternatives.

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