zotero_semantic_search

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

With no annotations provided, the description carries the full transparency burden and does well: it explains active-library default behavior, cross-library search behavior, the SQLite backend requirement, the need to populate the database first, and the optional dependency caveat. It doesn't explicitly state read-only semantics, but 'search' plus the lack of mutation language makes that reasonably clear, and an output schema covers the return shape.

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 long but every sentence earns its place: core purpose is front-loaded, parameter behavior is compactly explained, prerequisites are stated, and a concrete example closes it out. There is no filler or repetition of schema fields.

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 tool's complexity—five parameters, a required prerequisite database, backend constraints, and optional dependency—the description covers all essential context: scope defaults, how to broaden scope, when it is unavailable, and where to look for related library IDs. Because an output schema exists, omitting return-value details is acceptable.

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 coverage is 100%, so the baseline is 3, but the description goes beyond the schema with useful practical detail: natural-language query phrasing, default limit of 10, a concrete filters example, the '0'/'user' personal-library convention, and the mutual exclusivity of search_all_libraries with library_id. The only minor blemish is a slight key-style inconsistency in the filter example ('itemType' vs schema's 'item_type'), but it is clearly illustrative.

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 opens with 'Prioritized topic-search tool' and clearly states the tool finds papers by semantic similarity using AI embeddings. It explicitly distinguishes this from scanning collection items or reading abstracts, making its unique role among the sibling search tools unmistakable.

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 frames when to use the tool: 'the BEST tool for finding papers on a topic' and more efficient than manual scanning. It also gives operational prerequisites and access constraints. However, it does not explicitly name alternative search tools or state when to choose zotero_search_items or zotero_advanced_search instead, so the exclusion guidance is implied rather than explicit.

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