Zotero Authorize Local Writes

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

With no annotations, the description carries the full behavioral burden and does so thoroughly: it warns that the call BLOCKS until a user answers a dialog, instructs the agent to tell the user to switch to Zotero, explains the Always Allow vs Allow key semantics, and discloses the rate limit of about 5 prompts per minute with a do-not-retry warning.

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 dense but every sentence adds necessary information: purpose, blocking behavior, user guidance, grant semantics, precondition, exclusions, parameter semantics, rate limit, and a usage example. The most critical warning (BLOCKS) is front-loaded.

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?

The description covers the trigger condition, user interaction, parameter meaning, behavioral side effects/constraints, and exclusion cases. Since an output schema exists, the lack of explicit return-format detail is not a gap, and the description is complete for correct invocation.

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 coverage is 0% because the input schema only provides types and defaults, so the description must explain the parameters. It does: app_name is the name shown in the dialog, and timeout is described as seconds to wait with a valid range (5-55) and default 45.

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 names a specific action (request permission), a specific target (local Zotero library, Zotero 10+), and the context that triggers it. It distinguishes itself from sibling write tools by clarifying it is about authorization, not performing writes, and notes when web API mode makes it unnecessary.

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?

It gives an explicit trigger: call when a write tool reports no writable backend and zotero_write_capabilities indicates local writes are supported but no key is held. It also states when it is not needed (web API mode) and warns against retrying in a loop, providing clear when-to-use and when-not-to-use guidance.

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