List saved searches

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

Annotations already declare readOnlyHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds useful behavioral context: saved searches are returned 'with their conditions,' and the local API can actually execute them, which is a meaningful caveat beyond the structured fields.

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 with no filler. It front-loads the core purpose, includes the key sibling pointer, and adds the local-API caveat without bloating the text. Every sentence earns its place.

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 tool is a straightforward read-only listing operation with no required parameters, a fully documented input schema, an output schema, and annotations covering safety. The description clarifies the return content ('conditions') and the relationship to zotero_run_saved_search, so an agent has everything needed to select and 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?

Schema description coverage is 100%, so the parameter documentation already handles limit, start, groupId, and verbose. The description does not add parameter-level meaning beyond the schema, but it does not need to because the schema is thorough. Baseline 3 is appropriate.

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 a specific verb ('List'), a clear resource ('saved searches defined in the library'), and elaborates that the result includes their conditions. It also points to the related execution tool, zotero_run_saved_search, and distinguishes the local API advantage, so the tool's role is unambiguous.

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?

It clearly says to run a saved search with zotero_run_saved_search, giving an explicit alternative for the related action. It also notes the local API can execute saved searches whereas the web API cannot, which helps an agent decide context. It does not lay out exclusions, but for a simple list operation the guidance is sufficient.

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