WP-Nerve exposes 5 tools with mixed quality. Tools 1-2 (tools/list, tools/call) have reasonable descriptions and structured schemas with annotations, but tools 3-5 (server/discover, initialize, ping) are legacy protocol remnants with minimal descriptions. The tools/call schema includes _meta fields for idempotency and confirmation, showing security-aware design. However, parameter descriptions are sparse, and output schemas are not documented. The registry pattern (AbilityToolRegistry) is well-structured and maps WordPress abilities to MCP tools with policy authorization, but the exposed tool definitions lack the depth needed for reliable LLM selection.

• Remove initialize and ping tools, they are deprecated in MCP 2026-07-28. Protocol version negotiation and connectivity checks should be handled at the transport layer, not as tools.
• Document output schemas for tools/list (returns array of ability names/descriptions) and tools/call (returns {result, risk} structure). Include example responses.
• Add descriptions to all parameters in tools/call: explain what 'name' accepts (WordPress ability names), what 'arguments' structure depends on the ability, and when/why to populate _meta fields.
• Enhance error messages with recovery guidance. E.g., if tools/call returns 'ability not found', suggest 'Call tools/list to discover available abilities for your role.'
• Document the risk classification system (read, write, destructive, privileged) in tool descriptions so LLMs understand the implications of each tool's risk level.

Inferred effective spec: 2025-06-18+.

• Relies on Dynamic Client Registration (deprecated) - use Client ID Metadata Documents (CIMD)