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 burden of behavioral disclosure. It only says the search is 'AI-powered' and 'semantic' but does not explain how results are ranked, whether it searches the user's Zotero library, or what the response contains.

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 short and front-loaded, but 'AI-powered' is filler that does not add actionable information. It is concise yet under-specified, and it lacks structured details that would help an agent use the tool confidently.

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 simple with only two parameters and a fully documented schema, so the description does not need extensive detail. However, without an output schema or annotations, the description should at least clarify the search source and result behavior; it does not.

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%, with both 'query' and 'limit' already documented in the input schema. The description adds only the notion of semantic similarity, which is marginal beyond what the schema already conveys.

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 action ('search') and a resource ('papers'), and adds the qualifier 'semantic' to distinguish it from a plain keyword search like zotero_search. It is not a tautology and communicates the core function, though 'similar papers' is slightly ambiguous about the input source.

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?

There is no guidance on when to prefer this tool over zotero_search, find_related_papers, or search_personal_library. No exclusions or alternative selection criteria are provided, so an agent must infer use cases from the name alone.

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