Manage Zotero saved searches

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

Description discloses that writes go to the cloud Web API, consistent with readOnlyHint=false. It does not mention rate limits or error states, but the three actions (list, create, delete) are clearly described. No contradiction with 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?

Two sentences with front-loaded purpose and critical caveat. Every sentence provides value, no repetition or filler. Efficiently conveys all necessary information.

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?

No output schema exists; description does not mention return values for list/create/delete. Given 6 parameters and nested conditions, some description of expected output would improve completeness, especially for 'list' action.

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 50% (3 of 6 parameters described). The description adds context for conditions format and which parameters are needed per action, but does not explain library_id or library_type. Partially compensates for coverage gap.

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 clearly states it lists, creates, or deletes saved-search definitions, with specific actions and prerequisites. It distinguishes itself from sibling tool zotero_search_items by explaining that this tool only manages definitions, not executes queries.

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?

Provides explicit guidance on when to use this tool versus alternatives: mentions that the Zotero cloud Web API does not execute searches, directing users to zotero_search_items for actual matching results, and suggests desktop local API as alternative.

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