zotero_update_saved_search

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

The description discloses two key behavioral traits: partial updates ('Only the parts you pass are changed') and wholesale replacement of conditions when provided. These are not apparent from annotations (none are provided) and go beyond the schema, which merely labels conditions as 'Replacement conditions'.

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 compact sentences deliver the essential action and the critical replacement nuance. Every word adds value, and the 'conditions replaced wholesale' caveat is front-loaded immediately after the action statement.

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?

While the update semantics are well explained, the description omits how to specify which saved search to update (search_key), which is required for any call. No output schema exists, but the missing required parameter is a significant gap that prevents correct invocation.

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 description adds the partial-update semantics for 'name' and 'conditions', but the required 'search_key' parameter is entirely undocumented in both the schema (it appears only in 'required') and the description. With only two of three parameters described in the schema, the description does not compensate for the missing identification parameter.

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 ('Update') and resource ('a saved search') and clearly enumerates the mutable fields ('name and/or its conditions'). This distinguishes it from sibling tools such as create_saved_search, delete_saved_search, and run_saved_search.

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 implies the use case (modifying an existing saved search) but does not explicitly contrast with alternatives like creating a new search or deleting one. It provides no exclusions or when-not-to-use guidance, so the agent must infer the intended context from the title.

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