zotero_search

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

With no annotations, the description carries the burden. It discloses that the search covers title, author, and year and that tag/collection filtering is optional. However, it does not describe the return format, pagination, or what happens with no results, leaving important behavioral gaps.

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 the main action and scope, and wastes no words. Each clause adds meaningful information about search behavior and filters.

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 search tool with fully documented parameters and no output schema, the description adequately covers the core functionality: search query, fields, and optional filters. It does not explicitly state the return object, but the simple nature of search and the presence of a limit parameter mitigate this gap.

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 schema descriptions already cover all four parameters with examples and defaults. The description adds value by clarifying that the query searches title, author, and year and that tag and collection are optional filters, providing meaning beyond the schema's field definitions.

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 searches a Zotero library by query string and specifies the fields searched (title, author, year). It distinguishes itself from siblings like zotero_get_item (item retrieval) and zotero_collections (collection listing) by focusing on 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 usage for searching the library but does not explicitly contrast with sibling tools or state when to use alternatives. There is no mention of when not to use this tool, so guidance is limited to implied context.

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