Call the Zotero Web API

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

Annotations only declare readOnlyHint=false and openWorldHint=true; the description goes further by disclosing that DELETE is refused without confirm_delete=true, that updates must carry the current version, that write_token guards against duplicate creates, and that responses reflect the API-key account rather than the local app. It does not mention rate limits or permission scopes, but it adds substantial behavior 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?

Front-loaded with the core action, then a compact block of method-specific instructions. The sentences are terse but a few are telegraphic ('Create items with POST items and a JSON array'), trading a little polish for density.

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 generic API passthrough with an output schema present, the description covers the essentials an agent needs: auth-account binding, method/path conventions, body shape, delete confirmation, and version preconditions. Return values are covered by the output schema, so nothing material is missing.

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 100%, so the baseline is 3, but the description adds real meaning the schema lacks: body should be an array for item creates, collection keys belong in each item's collections array, and the version must be sent when updating. That is genuine parameter guidance rather than a restatement of the schema.

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?

'Send one Zotero Web API v3 request to the configured user library' names a specific verb, resource, and target, and explicitly positions it against the bibliography tools that read the local app. An agent can distinguish it from search_zotero/list_zotero_items without opening the schema.

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 states the key routing rule (local-app bibliography tools for reads vs. this tool which always hits api.zotero.org) and spells out concrete usage patterns for POST items, PATCH items/ITEMKEY, PUT, and DELETE. It stops short of naming individual sibling tools or giving explicit exclusions, so it is clear context rather than full when/when-not guidance.

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