zotero_authorize_local_writes

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

With no annotations provided, the description carries the full disclosure burden and does so thoroughly. It reveals that the tool blocks until the user answers a dialog, explains the difference between Always Allow and Allow keys, notes rate-limiting, and instructs the agent to tell the user to switch to Zotero.

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 context: purpose, blocking behavior, user guidance, key semantics, invocation conditions, parameter meanings, rate limits, and an example. The most critical information is front-loaded, and the example anchors the expected call form.

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 the tool's interactive/blocking nature and the presence of an output schema, the description covers all needed operational knowledge: when to call, what the user will see, the two key types, timeout bounds, rate limits, and when to skip the call. No major gap remains.

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 explain both parameters, and it does. app_name is defined as the name shown in the dialog, and timeout is defined as seconds to wait with an explicit range (5-55) and default. This is meaningful guidance beyond the bare 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?

The description opens with a clear verb-resource pair: request permission to write to the local Zotero library. It also specifies scope (Zotero 10+) and distinguishes the tool from sibling write tools by framing it as an authorization step rather than a direct write 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 gives explicit when-to-use conditions: call it 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 due to rate limits.

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