Zotero Chunk RAG

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description only states what the tool does ('Get statistics') without explaining what kind of statistics are returned, whether this is a read-only operation, if there are rate limits, or how the data is formatted. For a tool with no annotation coverage, this leaves significant gaps in understanding its behavior and output characteristics.

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 a single, efficient sentence that directly states the tool's purpose without any unnecessary words. It's appropriately sized and front-loaded, making it easy to understand at a glance. Every part of the sentence earns its place by conveying essential information.

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?

Given that the tool has no parameters, an output schema exists (which should cover return values), and the description is concise, the description is somewhat complete for its simplicity. However, it lacks context about what 'statistics' entail and how this tool fits with its siblings, leaving room for improvement in guiding the agent on usage and output interpretation.

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 0 parameters, and the schema description coverage is 100% (as there are no parameters to describe). The description doesn't need to add parameter semantics beyond what the schema provides. According to the rules, with 0 parameters, the baseline score is 4, as there's no parameter information to compensate for or enhance.

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 the action ('Get statistics') and the target resource ('about the indexed collection'), which provides a specific verb+resource combination. However, it doesn't differentiate this tool from its siblings (get_passage_context, search_papers, search_topic), which all appear to operate on similar data but serve different purposes. The purpose is clear but lacks sibling differentiation.

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 provides no guidance on when to use this tool versus its siblings or alternatives. It doesn't mention prerequisites, context for usage, or exclusions. While the tool has no parameters, which might imply straightforward usage, there's no explicit instruction on when this statistical information is needed compared to other tools that search or retrieve content.

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