WooAgent MCP server has critical definition gaps. Tool descriptions are present but minimal (10-50 chars, well below the 194-char baseline). Input schemas exist but lack parameter-level type definitions and descriptions, parameters like 'query' and 'body' are typed as generic objects with no field documentation. No output schemas are documented. Error handling is absent. The server exposes write operations (create_product, update_order, create_coupon) without confirmation patterns or permission gates. No tool annotations (readOnlyHint, destructiveHint) despite clear read/write distinction. Parameter descriptions are missing entirely for nested objects, forcing LLMs to guess valid fields.

• Expand tool descriptions to 100-200 chars. Include WHAT the tool does, WHEN to use it (vs similar tools), and key constraints. Example: 'Retrieve products from WooCommerce store. Use this to search by name, category, or price range. Returns paginated results (default 20 per page). Supports filtering by status (publish, draft, pending).'
• Document output schemas for all tools. Define response structure with field names, types, and descriptions. Example for get_products: {products: [{id: string, name: string, price: number, status: enum}], total: number, page: number}
• Replace generic 'body' and 'query' parameters with explicit field definitions. For create_product, list required fields (name, price, description) and optional fields (sku, category_id, images) with type and constraint info.
• Add tool annotations: mark read-only tools with readOnlyHint=true; mark destructive tools (create_*, update_*, delete_*) with destructiveHint=true and idempotentHint=false unless idempotent.
• Implement error handling with recovery guidance. Return structured errors: {error: string, code: string, retryable: boolean, suggestion: string}. Example: 'Product not found. Try search_products() with a partial name or category filter.'

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry