zotero_ping

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

The annotations already declare readOnly, idempotent, and non-destructive behavior, so the bar is lower. The description adds value by specifying that the test targets the 'configured Zotero Local API' and is from the 'current environment', which gives context about connectivity. No contradictions with annotations. It does not detail timeout or error behavior, but for a simple ping with an output schema, this is adequate.

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, direct sentence that immediately conveys the tool's purpose. There is no redundancy or irrelevant information. Every word contributes to understanding the tool's function.

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 the tool's simplicity (no parameters, output schema present, rich annotations), the description is complete. It explains what the tool does and from where, which is sufficient for a ping/health-check tool. The output schema covers return details, so no additional description is needed.

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, and the schema coverage is 100% (empty schema). The description adds no parameter details because there are none to explain. According to the rubric, a baseline of 4 applies for 0 params, and this description satisfies that baseline.

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 tool's function: 'Test access to the configured Zotero Local API from the current environment.' It specifies a verb ('test'), a resource ('Zotero Local API'), and scope ('from the current environment'). This distinguishes it from the sibling tools, which perform searches, item retrieval, or collection operations rather than connectivity checks.

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 usage is implied by the name and description: it is a ping/health check for the Zotero Local API. However, the description does not explicitly say when to use it (e.g., before calling other Zotero tools) nor does it mention alternatives or exclusions. Thus, the guidance is only implicit.

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