Zotero Keeper shows moderate definition quality with decent descriptions and some structural work, but significant gaps in schema completeness and parameter documentation. All 10 tools have emoji-prefixed descriptions (10-200 chars), which is good for readability but occasionally vague. Input schemas are present for most tools, but many lack detailed type information or validation constraints. The descriptions reference output structures (library_version, server_id, attachment_count) that are helpful for chaining, but parameter-level documentation is sparse. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) are declared, despite tools having clear read/write semantics. The batch_import_from_pubmed tool is complex and write-heavy but lacks confirmation or dry-run support. Average parameter description length appears ~50 chars (below the 72-char baseline), and many parameters lack explicit min/max constraints.

• Add tool annotations to all tools: declare readOnlyHint=true for the 9 read-only tools and destructiveHint=true, idempotentHint=false for batch_import_from_pubmed.
• For batch_import_from_pubmed, add a dry-run boolean parameter (default false) and a confirmation_token return field. Return a summary of what would be imported before confirming; require the token on a second call to actually execute.
• Document validation constraints for all numeric and string parameters. Add min/max to 'limit' (e.g., 1 - 500), format regex to 'key' (e.g., ^[A-Z0-9]{8}$), and enum constraints to categorical params.
• Formalize output schemas as JSON Schema objects in the tool definition. For get_item_attachments, define { 'type': 'object', 'properties': { 'item_key': {'type': 'string'}, 'attachment_count': {'type': 'integer'}, 'attachments': {'type': 'array', 'items': {...}}, ...}, 'required': ['item_key', 'title', 'attachment_count', 'attachments'] }.
• Expand descriptions for discovery/list tools. E.g., list_tags → '📋 List all tags in your Zotero library. Call this before searching by tag or to understand available tag structure. Returns array of tag objects with usage counts. Useful for taxonomy discovery and tag-based filtering.' (~180 chars, actionable context).
• Clarify collection parameter handling in batch_import_from_pubmed. Add explicit parameter descriptions: collection_name='Use this (recommended), automatically resolves to collection_key and validates it exists', collection_key='Advanced only, raw collection UUID, no validation', allow_library_root='Only set true if you explicitly want imports outside all collections (unusual)'.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry