zotero_status

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

With no annotations provided, the description carries the full burden. It clearly states the tool performs a diagnostic check, reports on connector configuration, and includes guidance on what to fix if something is missing. This is a read-only operation, which is implied but not explicitly stated as non-mutating.

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?

A single sentence that is concise and packs in all key information: what it reports and the diagnostic nature. No waste, front-loaded with the verb 'Report'.

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, no-output-schema tool, the description is complete for guiding an agent on what it does and its diagnostic purpose. It covers the behavioral aspects sufficiently, though it doesn't detail the exact return format, which is not required given no output schema.

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 there is nothing to document in the schema. The description adds value by explaining what the tool reports, compensating for the absence of parameters. Baseline of 4 is appropriate for no-parameter tools.

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?

States a specific verb ('Report') and resource ('how this connector is configured'), enumerating concrete outputs (data directory, item counts, API key status, fixes). Distinguishes from siblings by being a diagnostic/status tool rather than a data retrieval or mutation tool, though it doesn't explicitly name a sibling.

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?

Implies usage for checking configuration status, but provides no explicit guidance on when to prefer this over siblings like zotero_search or zotero_recent. No mention of alternatives or when not to use.

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