Two tools with minimal schema and description quality. wp_get_posts has empty input schema ({}), violating the no-schema rule. wp_create_draft has basic parameter descriptions but lacks output schema documentation. Neither tool description explains WHEN to use it, what it returns, or error handling. Descriptions are 30-50 chars, below the 50-200 char baseline for LLM-optimized tools. No parameter constraints (enums, ranges), no error guidance, no idempotency hints despite wp_create_draft being a write operation. Tool names follow verb_noun convention (positive), but lack context about WordPress-specific behavior.

• Add pagination to wp_get_posts: accept 'page' (default 1), 'limit' (default 20, max 100), and return 'total_count', 'posts' array with post_id, title, status, created_date. Document output schema.
• Expand wp_get_posts description to 100+ chars: 'Retrieve a paginated list of WordPress posts. Returns post metadata (ID, title, status, date). Use to discover posts before editing or to check publication status. Supports filtering by page and limit.'
• Add output schema to wp_create_draft: return {post_id, title, status: 'draft', created_date, edit_url}. Document that the post is NOT published and can be edited via update_post tool.
• Expand wp_create_draft description: 'Create a new WordPress post as a draft (unpublished). Requires title and content. Returns post_id for later editing. Draft posts are not visible to readers until published via publish_post tool. Supports markdown or HTML content.'
• Add parameter constraints: title (required, 1-200 chars), content (required, 1-50000 chars). Document in descriptions: 'title: Post headline (1-200 characters, required)' and 'content: Post body in markdown or HTML (1-50000 characters, required)'.