zotero_search

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

No annotations are provided, so the description must carry the burden of disclosing side effects. It describes a search operation, which strongly implies read-only behavior, but it does not explicitly state that no modifications occur, nor does it mention permissions or rate limits. This leaves some ambiguity.

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 concise, consisting of two clear sentences with no unnecessary details. It front-loads the main purpose and efficiently conveys the core functionality without verbosity.

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 description gives some context by mentioning that the output keys are used by PDF tools, which helps the agent understand the tool's role. However, it does not detail the output structure, pagination, error handling, or query syntax, leaving some gaps in the complete picture of how to use the tool.

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 description does not explain the 'query' or 'limit' parameters at all. It merely says 'Search the Zotero library' without detailing what the query should contain or how limit affects results. Since the schema provides no descriptions either, the parameter semantics are entirely missing.

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 'Search the Zotero library', which specifies the verb ('search') and the resource ('Zotero library'). It also distinguishes this tool from siblings by noting it returns item keys used by PDF tools, making its purpose 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?

The description implies when to use the tool by stating that the returned keys are input for PDF tools, guiding the agent toward this tool for finding items. However, it does not explicitly contrast with alternatives like zotero_item_info or provide conditions for when not to use it, so it is not fully explicit.

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