zotero_add_note

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

With no annotations, the description carries the full burden of behavioral disclosure. It states the action and the requirement for a write-access API key, but does not describe side effects, potential errors, or what happens on success. For a mutation tool, it lacks depth about reversibility, idempotency, or response format, leaving the agent without critical safety or outcome information.

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 two sentences with no fluff. The primary action is front-loaded, and the API key requirement is stated efficiently. It is concise and easy to parse, though it could benefit from a brief usage context sentence.

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 this is a write operation with no annotations and no output schema, the description should provide more context about expected outcomes, error handling, and when to use the parentKey versus standalone mode. The API key requirement is helpful, but the description is incomplete for an agent to call it correctly and confidently, especially without knowledge of the response format or failure modes.

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 schema description coverage is 75%, covering text, library, and parentKey. The description text itself does not add any parameter-specific meaning beyond what the schema provides; it merely restates the overall purpose. Since the schema already documents these parameters, the description does not compensate for the missing tags parameter description, but the baseline for high coverage is a 3.

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 action: attaching a note to an existing Zotero item or adding a standalone note via the web API. It specifies the resource (Zotero item) and differentiates from creating a full item or tagging. It does not explicitly name a sibling tool, but the purpose is 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 implies when to use this tool (to add a note) but provides no explicit guidance on when not to use it or how it compares to alternatives like zotero_create_item or zotero_update_item. There is no mention of exclusions or preferred scenarios, so an agent must infer the appropriate context.

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