Three tools with clear verb-noun naming (wpcom_list_sites, wpcom_get_site, wpcom_get_atlantis_status) and solid descriptions (120-180 chars). All tools have input schemas with type definitions and parameter descriptions. However, output schemas are not documented in the source code, LLMs cannot predict return structure. Parameter descriptions are present but lack format constraints (e.g., no enum for 'type' in wpcom_list_sites, no pattern for site_id_or_url). Error handling is not visible in the tool definitions. No tool annotations (readOnlyHint, destructiveHint) despite all being READ_ONLY operations.

• Add output schema documentation for each tool. Example for wpcom_list_sites: 'Returns array of site objects with fields: site_id (number), name (string), url (string), type (string: jetpack|agency|other).'
• Convert 'type' parameter in wpcom_list_sites to an enum: {"enum": ["all", "jetpack", "agency"]} instead of free-form string.
• Add readOnlyHint: true to all three tools via ToolAnnotations to signal to MCP clients that these are safe, idempotent read operations.
• Enhance site_id_or_url parameter description: 'The domain name (e.g., example.com) or WPCOM numeric site ID (e.g., 12345). Both formats are accepted.'
• Document error scenarios in tool descriptions. Example: 'Returns error if site not found or user lacks access. Call wpcom_list_sites() to discover available sites.'