Check Zotero adapter health

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

Annotations already mark the tool as read-only, but the description adds the valuable behavioral guarantee 'Never errors,' clarifying that this is a non-throwing status probe. It also discloses the exact components being checked, though it does not describe the shape or interpretation of the returned health status.

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 exceptionally concise: two short sentences with no filler. The main purpose is front-loaded, and the behavioral guarantee is added separately without bloating the text.

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 health-check tool, this is largely complete: the agent knows what is checked, that it is read-only, and that it will not error. The only gap is the return payload and how to interpret it, which would make the health-check result fully actionable.

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 schema coverage is 100%, so there is no parameter documentation burden. The baseline of 4 applies because the description does not need to explain any parameter semantics.

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 names a specific verb ('Check') and enumerates the exact resources involved: Zotero, its local read API, the Research Workbench write API, and bearer authentication. This clearly distinguishes it from the sibling tools, which all perform item/collection/tag operations.

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 implies this is a health/preflight probe because it checks connectivity and authentication, but it does not explicitly state when to use it versus alternatives or whether it should precede other Zotero calls. No sibling is a health check, so the ambiguity is limited.

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