wp-mcp has 5 tools with basic schemas and descriptions, but significant gaps prevent higher scores. All tools have descriptions (10-80 chars, mostly short), and input schemas are present with Zod validation. However, descriptions are sparse and lack context for LLM selection. No output schemas are documented. Error handling is minimal, failures return generic text without recovery guidance. Tools lack idempotency hints, permission declarations, and composition guidance. The server mixes weather (NWS) and WordPress APIs without clear separation or dependency documentation.

• Add output schemas to all tools. Document the structure of alerts, forecast periods, posts, and categories. Example: 'Returns array of {event, area, severity, status, headline}' for get-alerts.
• Expand tool descriptions to 50 - 150 chars. Include WHAT (retrieves weather alerts), WHEN (when you need current severe weather warnings), and WHAT IT RETURNS (list of active alerts with severity). Example: 'Retrieves active severe weather alerts for a US state. Use this to check for tornado warnings, flood alerts, etc. Returns array of alerts with event type, area, severity, and headline.'
• Add error recovery guidance. Replace 'Failed to retrieve alerts data' with 'Unable to fetch alerts from NWS API. Verify the state code is valid (2-letter US state abbreviation). If the issue persists, the NWS API may be temporarily unavailable.'
• Add tool annotations. Mark all tools with readOnlyHint=true and idempotentHint=true in the schema to signal they are safe to retry and have no side effects.
• Add pagination parameters (limit, offset/cursor) to get-latest-posts and get-categories. Document the default and maximum limits. Example: 'limit: number (default 10, max 50), number of posts to return'.