zotero_write_capabilities

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

No annotations are provided, so the description carries the full burden. It discloses 'Read-only and instant — it never opens a dialog,' which covers safety and UI behavior. It could add detail on how the result is returned, but an output schema exists to cover that.

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?

Despite its length, every sentence earns its place: purpose, behavioral traits, trigger condition, routing logic, and an example. Information is front-loaded with the core purpose before the usage details.

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?

Output schema exists so return format needs no explanation. The description covers purpose, safety, when-to-use, and post-call routing. Nothing an agent needs to correctly invoke this zero-arg diagnostic 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?

Zero parameters, so the baseline is 4. The description reinforces this with 'Takes no arguments' and a concrete example call 'zotero_write_capabilities()', leaving no ambiguity about invocation.

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?

States a specific verb ('Report') and resource (whether/how the server can write to Zotero), enumerating the four distinct modes (local API, web API, hybrid, nothing). This fully distinguishes it from the sibling write tools and diagnostic tools like zotero_get_search_database_status.

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?

Gives an explicit trigger condition — 'when a write tool reports that no writable backend is configured' — and provides a decision tree: call zotero_authorize_local_writes if local writes are possible but no key is held, otherwise web API credentials are needed. This is model-guidance at its best.

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