Zotero Get Search Database Status

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 states 'no side effects', describes the conditional install-hint behavior when the semantic extras are absent, and indicates the output format is a human-readable status block. This covers the essential behavioral traits, though it could add minor operational details such as potential latency or failure modes.

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 compact and every sentence earns its place: purpose, guiding decision, parameter/side-effect note, return behavior, and an illustrative example. It is front-loaded with the primary purpose and avoids unnecessary filler.

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?

For a zero-parameter status tool with an output schema, the description is complete. It covers what the tool reports, when to invoke it, side effects, the fallback behavior, and an example result. The sibling tool list provides enough surrounding context for an agent to select it correctly.

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 tool has zero parameters, so the schema already documents everything. The description reaffirms 'Takes no parameters' and explains what the no-input call will yield, which is sufficient given the empty input schema.

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: 'Report the semantic search database's readiness and stats', then enumerates the exact stats returned (item count, last update time, embedding provider/model, optional dependency installed). This clearly distinguishes the tool from siblings like zotero_semantic_search and zotero_update_search_database.

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 explicitly states when to use the tool: 'Use this to decide whether zotero_semantic_search will return useful results, or whether the user should run zotero_update_search_database first.' It names the applicable alternatives and the decision condition, leaving no ambiguity.

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