zotero_list_libraries

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

No annotations provided, so description carries full burden. It declares read-only and no side effects. Describes differences between local mode (reads local SQLite DB, includes RSS feeds) and web mode (queries API, no feeds). Notes active library isn't flagged, advising manual tracking. Comprehensive.

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?

Well-structured with clear sections: purpose, workflow, alternatives, mode differences. No redundant sentences. Front-loaded with key information. Concise yet complete.

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 no parameters, presence of output schema, and thorough coverage of behavior (modes, side effects, output fields, workflow), the description is fully complete for the tool's simplicity.

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?

No parameters, so schema coverage is 100%. Description adds meaning by summarizing what each library entry contains (library/group ID, display name, item count). Baseline for 0 parameters is 4, and description provides useful context beyond the schema.

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?

Description clearly states the tool lists libraries the MCP can address (personal, group, RSS feeds). It distinguishes from sibling tool zotero_get_collections by noting that tool lists collections within current library. Uses specific verb 'list' and resource 'libraries'.

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?

Explicitly states to use this tool to discover a library ID before calling zotero_switch_library, forming a read-then-switch workflow. Also says if user wants only collections in current library, use zotero_get_collections instead. Provides clear when-to-use and 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.