Run a saved search

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

Annotations already declare the operation read-only and idempotent. The description adds useful behavioral context beyond that: the search executes against the local database using Zotero's own engine, and results match what the saved search shows in the Zotero UI. This helps set expectations about fidelity and scope.

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 no wasted words. The first sentence states the core operation, and the second provides the key behavioral guarantee. Information is front-loaded and easy to scan.

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 strong annotations, complete parameter schema, and existence of an output schema, the description is sufficient. It adds the only context not already represented in structured metadata: local execution and UI-matching results. Nothing essential is missing for an agent to invoke this tool correctly.

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 100%, and each parameter already has a meaningful description, including searchKey origin, paging semantics, and verbose token cost. The description adds no parameter-level information, which is acceptable given the rich 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 clearly states the verb ('Execute') and resource ('a saved search'), and clarifies that it returns matching items. It distinguishes from ad-hoc searching by focusing on saved searches and Zotero's own search engine, though it does not explicitly name a sibling alternative.

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 intended use is implied: run this when you want to execute an existing saved search and get its results. However, there is no explicit statement about when to use this tool versus zotero_search_items, nor any when-not guidance beyond the existence of a saved search key.

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