Request Zotero write access

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

Annotations already declare idempotentHint=true and readOnlyHint=false, but the description adds substantial behavioral detail: it raises a modal dialog with three choices, explains the difference between single-use and persistent keys, describes local storage and reuse, and notes that write tools auto-reauthorize. This goes well beyond the structured 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?

Four sentences, all information-dense and front-loaded. The first sentence states the core purpose; subsequent sentences cover dialog behavior, user guidance, and reuse semantics. No filler or repetition of schema content.

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 an authorization tool with an output schema and clear annotations, the description is complete. It explains the dialog, user choices, key lifecycle, when manual invocation is needed, and the no-op case when a key already exists. Nothing essential 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?

The schema has 100% coverage for the single optional `force` parameter, so baseline is 3. The description adds practical context about key reuse and the no-dialog behavior, which reinforces when `force` would matter, though it does not name the parameter directly. The schema and description together fully explain the parameter's semantics.

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 specific verb and resource: 'Request a local API key so write tools ... can run.' This clearly distinguishes it from sibling tools, which all operate on collections, items, or libraries. The title 'Request Zotero write access' reinforces the purpose without ambiguity.

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 explicitly states when to call it manually ('only needed to grant access up front'), when not to ('calling it when a key is already stored reuses that key and shows no dialog'), and gives user-facing guidance ('Tell the user to expect the dialog, and to pick "Always Allow" for a session that will perform several writes'). It also notes that write tools re-authorize on their own, so alternatives are clear.

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