Zotero Save

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

Beyond the annotations (readOnly=false, destructive=false), the description elaborates that the tool writes a journal-article item with specific fields (title, authors, year, venue, DOI) and requires Zotero 7+ for writes. This gives practical insight into the write behavior and system dependency, which is valuable context not captured by 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 two sentences: the first delivers the core function, the second covers prerequisites and usage pairing. It is front-loaded and contains no redundant or filler content, earning a 5.

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?

For a one-parameter tool with no output schema, the description covers the essential context: input types, what is saved, system requirements, and related tools. It does not specify the return value or error behavior, but for this simple save operation that is a minor gap, so a 4 is given.

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 single parameter 'identifier' is fully described in the schema with the same list of accepted formats (DOI, OpenAlex ID, URL, title). The description repeats these formats but adds no new semantics beyond confirming that the tool resolves the identifier to a paper, so the baseline of 3 is appropriate.

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 explicitly states the action ('save it to the user's local Zotero library') and the input types (DOI, OpenAlex ID, URL, title), clearly distinguishing it from sibling tools like search-literature and fetch-paper by naming the resource and operation.

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 contextual usage by stating 'Pair with search-literature or fetch-paper to capture a source you want to keep,' indicating when to use the tool (after finding a paper). It also notes the prerequisite (Zotero running with local API enabled), but does not explicitly list when-not-to-use scenarios, so it fits just below a 5.

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