zotero_create_noteCreate standalone or child HTML notes in Zotero with optional tags and parent item, enabling structured note-taking directly through the authenticated extension.
Create a standalone or child HTML note through the authenticated extension.
| Name | Required | Description | Default |
|---|---|---|---|
| html | Yes | ||
| tags | No | ||
| parentKey | No |
Changes observed during successful MCP inspections.
v0.1.0Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations only indicate readOnlyHint=false and destructiveHint=false, so the description carries some burden. It adds that this creates HTML notes and can create child notes, but it does not disclose return behavior, side effects, or requirements like the parent item needing to exist. This is moderate value beyond 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 one short sentence with no filler. It front-loads the core purpose and the parent/child distinction, making it easy for an agent to parse quickly.
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?
With no output schema, no parameter descriptions, and only generic annotations, this one-sentence description is incomplete for a creation tool. It does not explain return values, required format of 'html', how tags are applied, or what happens when parentKey is provided. An agent would need to infer too much.
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 meaning for 'html' (the note content is HTML) and 'parentKey' ('child' notes), but it says nothing about the 'tags' parameter. The compensation is partial but useful.
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 uses a specific verb ('Create') and a specific resource ('standalone or child HTML note'), which clearly distinguishes this from sibling tools like zotero_create_item or zotero_attach_link. The 'standalone or child' wording also signals the optional parentKey behavior.
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 gives no guidance on when to use this tool versus alternatives such as zotero_create_item or zotero_get_item_notes. It states what it does but does not provide context, prerequisites, or exclusions to help route the agent.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.