zotero_search

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

With no annotations, the description fully discloses search behavior: free-text matching on title/creator/year by default, optional expansion to all fields via 'everything' parameter. It states that results are a compact list with 'keys'. While some details are missing (e.g., pagination beyond limit, error handling), the core behavior is well communicated.

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 well-structured with clear 'Args' and 'Returns' sections, front-loading the main purpose. Each sentence adds useful information. Could be slightly more concise, but no redundancy.

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 5 parameters (all optional) and existence of an output schema, the description adequately covers search mechanics and return value (compact list with key). It notes usage of the 'key' with sibling tools, providing context. Lacks comparison to siblings but is otherwise complete.

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 0%, so the description must add meaning. Each parameter is explained: 'query' (free-text search), 'item_type' (restrict to type), 'tag' (restrict to tag), 'limit' (maximum items), 'everything' (search all fields). This adds substantial value beyond parameter names.

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 tool's purpose: 'Search the Zotero library for top-level items.' It uses a specific verb ('search') and resource ('Zotero library'), and specifies scope ('top-level items'). This distinguishes it from siblings like zotero_get_item (retrieve specific item) and zotero_list_collections (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?

No explicit guidance on when to use this tool versus alternatives. The description mentions that returned items have a 'key' for use with other tools, but does not provide context for when search is preferred over other Zotero tools. No exclusions or when-not-to-use information is given.

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