Add Note to Zotero Item

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

The description discloses that the tool writes to the library and requires write-access API key, which complements the readOnlyHint=false annotation. It also explains return value (new note key) and error cases (404/403), adding meaningful behavioral context 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 well-structured with clear sections (purpose, write notice, args, returns, examples, error handling) and is front-loaded with the main purpose. It is somewhat lengthy and repeats parameter details already present in the schema, but every section serves a useful purpose and there is no fluff.

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's moderate complexity (3 params, 1 optional) and no output schema, the description fully covers invocation context: when to use, permissions, return value, errors, and examples. It also clarifies distinction from siblings, making it self-sufficient for an agent to use correctly.

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 covers 100% of parameters, so baseline is 3. The description adds value through a concrete example mapping natural language to arguments (parent_item_key='ABCD1234', note_text='...') and clarifies the purpose of each parameter. However, it largely repeats schema descriptions rather than adding new semantics.

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 opens with 'Attach a child note to an existing item,' which clearly states the action ('attach'), the object ('child note'), and the target ('existing item'). It distinguishes from siblings by explicitly saying not to use it when modifying the item's own fields, directing to zotero_update_item_tags for tags.

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 explicit 'Use when' and 'Don't use when' guidance, including an example with concrete arguments and a clear alternative tool (zotero_update_item_tags). This exceeds the minimum by giving both positive and negative usage criteria.

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