list_saved_searches

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

Annotations already declare readOnlyHint=true and openWorldHint=true. The description reinforces read-only but adds non-annotation context: it explains what 'saved searches' are, where they appear in the desktop app, and that each result's key can be passed to delete_saved_search. This cross-tool linkage goes 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?

The description is two sentences, front-loaded with a verb+resource, and every sentence provides distinct value: the definition/contrast, the read-only reminder, and the key usage hint. No wasted words or redundancy beyond the useful clarification.

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?

A simple list tool with no parameters, an output schema, and two relevant annotations is fully served by this description. It explains what the resource is, how it differs from search_items, and how results relate to delete_saved_search. The output schema handles return-value details, so no further description is required.

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 tool has zero parameters, so schema coverage is trivially 100%. The description correctly adds no parameter details because none exist. Baseline 4 for zero-parameter tools is appropriate; no additional semantics are needed.

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 'List saved searches', a precise verb and resource, and clarifies that these are Zotero's stored search definitions distinct from ad-hoc search_items calls. This unambiguously identifies the tool's function and differentiates it from siblings like search_items and list_collections.

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 contrasts with 'not ad-hoc calls to search_items', signaling when not to use this tool and pointing to the alternative. It also implies a follow-up workflow via delete_saved_search, offering clear contextual guidance for a listing tool.

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