Server exposes credentials (site_url, username, password) as tool parameters across 4 of 5 tools, violating critical secret-injection pattern. Tool descriptions are present but generic (avg 60 chars, below 194-char baseline). Parameter descriptions exist but lack constraints, ranges, or format guidance. No output schemas documented. Error handling is minimal, most failures return raw HTTP status codes without recovery guidance. Tools lack idempotency hints and confirmation steps for destructive operations (publish_article). No pagination support despite potential for large result sets (get_categories, get_tags).

• Move credentials to server-side environment variables (WP_SITE_URL, WP_USERNAME, WP_PASSWORD). Remove site_url, username, password from tool parameters. Use get_wp_config to retrieve config server-side, or inject via middleware.
• Document output schemas for all tools. For get_categories: return {status: string, categories: [{id: int, name: string, slug: string, count: int}]}. For publish_article: return {article_id: int, article_url: string, status: string, edit_url: string}.
• Add pagination to get_categories and get_tags: accept 'limit' (1-100, default 20) and 'offset' (default 0) parameters. Return 'total' count and 'has_more' boolean so LLM knows when to fetch next page.
• Convert status parameter in publish_article to enum: {type: 'string', enum: ['draft', 'publish', 'pending', 'private'], default: 'draft'}. Add format guidance to categories/tags: 'JSON array of category IDs, e.g. [1, 2, 3]'.
• Add error recovery guidance. Instead of 'Failed to fetch categories: {response.text}', return 'Failed to fetch categories (HTTP 401). Check credentials via test_connection tool.' For 404 errors, suggest available alternatives.