Index Zotero Library

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

With no annotations, the description carries the full burden of behavioral disclosure. It usefully describes incremental processing, chunking, deduplication, and progress tracking, but omits key operational traits such as whether it mutates a persistent index, required credentials, expected runtime, or failure behavior.

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 front-loaded with a clear purpose sentence followed by a compact feature list. Most content earns its place, though the qualifier 'intelligent' and the specific average chunk count add minor promotional noise.

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?

An output schema exists, so return values need not be explained, and the input schema is fully documented. However, the absence of annotations and usage guidance leaves operational context incomplete for a stateful indexing operation, particularly around prerequisites and side effects.

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%, so both parameters are already documented in the input schema. The description reinforces the incremental default and hints at force_rebuild behavior, but adds no syntax, limits, or interaction details beyond what the schema provides.

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 states a specific verb and resource: indexing a Zotero library. It also clarifies that the tool performs incremental updates and chunking, which distinguishes it from search-oriented siblings. However, it does not explicitly name or contrast itself with siblings such as search_fulltext or list_papers.

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 explains features but not when to use this tool versus alternatives. It does not say whether it should be run before searching, how often to run it, or what conditions favor a full rebuild over incremental indexing. The only implied guidance comes from the feature list, not explicit usage instructions.

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