zotero_create_note

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

With no annotations provided, the description must fully disclose behavioral traits. It reveals that content is auto-converted to HTML and line breaks/spacing are preserved. However, it omits details about error behavior (e.g., invalid parent_key), authentication requirements, rate limits, or confirmation of creation success. The mutation nature is implied but not explicitly stated.

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 three sentences with no wasted words: first sentence states purpose and formatting, second lists use cases, third explains behavior. It is front-loaded with the primary action and remains succinct.

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 simplicity (3 parameters, 1 required) and the existence of an output schema, the description covers the essential context: purpose, use cases, and key parameter behaviors. It does not describe the return value, but the output schema likely fulfills that. A brief mention of what to expect upon creation would improve completeness.

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 explains that 'Content is auto-converted to HTML' (adding meaning to the content parameter) and that parent_key attaches to a paper for organization. However, it does not mention the tags parameter or provide any syntax or constraints, leaving a gap.

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 verb 'Create' and resource 'note in Zotero', specifies formatting support (tables, lists, line breaks), and lists concrete use cases (literature reviews, summaries, research memos). It distinguishes itself from sibling tools, which are all retrieval-oriented (get, search), making its purpose unambiguous.

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 guidance: 'Use for: saving literature reviews, summaries, research memos, or any content' and 'Attach to a paper with parent_key for organized reference management.' It does not explicitly state when not to use or compare to alternatives, but since all siblings are read-only, exclusions are implicitly clear.

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