Manage Zotero saved searches

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

Annotations already mark this as read-write and destructive, and the description adds important context: the cloud Web API stores saved-search definitions but does not execute them, and writes go to the cloud Web API. It could disclose prerequisites such as authentication or library context more explicitly, but the key behavioral caveat is present.

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 front-loaded with purpose and the key caveat, then gives a compact breakdown of the three actions. Every sentence carries information and none is wasted or redundant.

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 operational caveat, the action semantics, and the relationship to zotero_search_items, which is the core knowledge needed. It falls slightly short because library_id and library_type are not mentioned, and there is no output-schema guidance for what list/delete return, but as a whole it is largely sufficient.

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?

With only 50% schema description coverage, the description compensates by explaining the action enum values' meanings and the data shape required for conditions ({condition, operator, value}). However, library_id and library_type are left without any explanation in either the schema or the description, which is a notable 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 names specific verbs (list, create, delete) and a specific resource (saved-search definitions), and immediately distinguishes itself from zotero_search_items by stating the cloud API does not execute saved searches. This lets an agent understand what the tool does and what it does not do.

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 tells when to use this tool versus zotero_search_items: use this to manage definitions, and use an equivalent zotero_search_items query to get matched items. It also gives action-specific usage requirements (list vs create with name and conditions vs delete with search_key), so an agent can select the right path.

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