search_zotero_library

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

With no annotations, the description carries the full burden and does so thoroughly. It discloses read-only behavior ('database is never modified'), point-in-time snapshot semantics, exclusions (attachments, notes, trashed items), and search matching restrictions.

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?

Each sentence adds a distinct, decision-relevant fact: scope, matching rules, return fields, exclusions, database default, and snapshot caveat. There is no filler or repetition.

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 covers purpose, query semantics, output fields, exclusions, configuration, and data freshness limits. With an output schema present and only three parameters, nothing essential to invoke the tool correctly is missing; the limit behavior is the only minor omission and is reasonably inferable.

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%, but the description compensates by explaining query matching semantics across title, creator, year, and publication, and by documenting db_path's default and nonstandard-data-directory usage. The limit parameter is not explicitly explained, though its name and default make its cap behavior inferable.

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 a specific verb and resource: 'Search the user's LOCAL Zotero library,' and immediately clarifies the read-only nature. It also names the consumer relationship to insert_zotero_citation, which distinguishes this tool's role among the large sibling list.

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 provides clear context: this tool finds Zotero items and returns item keys that insert_zotero_citation consumes, so an agent knows when to use it. It does not explicitly list when-not-to-use or contrast with sibling search tools, but no direct alternative is present among siblings.

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