zotero_save

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

Annotations already declare readOnlyHint=false and openWorldHint=true, so the agent knows this mutates state and touches an external service. The description adds a genuine prerequisite (configured API credentials) that the annotations do not convey, which is useful. However, it does not say whether it creates a new item vs updates an existing one, what happens on auth failure, or whether saves are idempotent.

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?

A single front-loaded sentence with no filler; the key action and prerequisite come first. It is efficient, though its brevity borders on under-specification rather than waste.

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?

An output schema exists so return values need not be explained, but for a mutating external-integration tool with two undocumented parameters the description is too thin. Missing are the meaning of paper_id, the collection semantics, and failure behavior when credentials are missing or the target collection is invalid.

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 carry the burden, and it does not. It never explains what 'paper_id' refers to (an ID from search results? a DOI?) nor what 'collection' does beyond the schema's bare default of 'Inbox', leaving both parameters semantically opaque.

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 gives a specific verb ('Save') and resource ('paper metadata to Zotero'), so the agent knows this is a write-to-Zotero operation rather than a search or read. It is not explicitly differentiated from siblings, but none of the siblings reference Zotero, so confusion is unlikely.

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?

'when API credentials are configured' states a precondition, which implies usage context, but there is no guidance on when to prefer this over other enrichment tools (e.g., align_and_enrich) or what to do when credentials are absent. Usage is implied rather than stated.

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