zotero_web_api_status

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description reinforces these by stating 'Read-only check' and 'Performs no write,' and adds valuable context by enumerating exactly what is checked (credentials, user ID, write permission, file-write permission). This goes beyond the annotations without contradicting them.

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 sentence that front-loads the core purpose ('Read-only check') and includes only essential details about what is verified and that no write occurs. Every phrase earns its place.

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 parameterless read-only status tool with an output schema and strong annotations, the description fully covers purpose, safety, and scope of the check. Nothing is missing for an agent to confidently invoke it.

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?

With zero parameters, the schema is trivially fully covered. The baseline for no params is 4. The description does not need to explain parameter meanings, and it appropriately focuses on the tool's purpose and behavior.

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 uses a specific verb ('check') and identifies the exact resources being verified (official Zotero Web API credentials, expected user ID, personal-library write permission, file-write permission). This clearly distinguishes it from sibling tools like zotero_ping, which likely tests connectivity rather than credential/permission status.

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 clearly implies the tool is for verifying credentials and permissions before performing write operations, by explicitly stating 'Read-only check' and 'Performs no write.' While it does not name alternatives or exclusion criteria, the context is clear enough for an agent to select it when a pre-flight credential check is needed.

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