zotero_delete_saved_search

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It explicitly discloses the most important side effect—deleting a saved search does not delete its items—and explains why via 'a saved search is just a query.' This goes beyond the tool name, though it does not discuss permanence or error behavior.

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 short sentences with no filler. The core action is front-loaded, and the clarifying caveat about items being untouched follows immediately and efficiently.

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 a single-parameter delete tool with an output schema, the description is fully sufficient. It identifies the target resource, explains the key non-side-effect, and no additional context is needed for an agent to invoke it 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?

The input schema already provides 100% coverage, including a description of search_key as 'Saved search key.' The tool description adds no further parameter-level detail, so the baseline of 3 is appropriate; the schema is doing the heavy lifting.

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 uses a specific verb and resource: 'Delete a saved search.' It also clarifies that items are untouched, distinguishing this tool from collection or item deletion tools in the sibling list. The explanatory clause 'a saved search is just a query' reinforces exactly what resource is being operated on.

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 makes clear when this tool is appropriate: when the goal is to remove a saved search definition rather than its underlying items. The phrase 'Its items are untouched' provides exclusionary context that helps an agent avoid zotero_delete_items or zotero_delete_collection, though it does not name alternative tools explicitly.

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