wb-mcp defines 20 tools with schemas and descriptions, but exhibits significant quality gaps. Tool names lack action verbs (wb_query, wb_todo, wb_fin are domain-prefixed, not verb-prefixed). Descriptions are present but often domain-focused rather than action-focused. Schemas are visible in WRITE_TOOL_SPECS but many generic tools (wb_query, wb_todo, wb_fin, wb_note, wb_manage, wb_dev_task, wb_vault, wb_archive) use identical generic parameter structures (command/args/confirm) with minimal specificity. Specialized write tools (wb_todo_done, wb_todo_edit, etc.) have better-defined schemas with enums and patterns. Error handling and output schemas are not documented. No tool annotations (readOnlyHint, destructiveHint) despite clear read/write distinctions.

• Rename generic tools to action-verb form: wb_query → search_workbench or query_workbench; wb_todo → list_todos or manage_todos. Pair with specific subcommand enums (list, done, edit, tag, del) to replace free-form 'command' strings.
• Replace command/args/confirm parameters with explicit, typed parameters for each subcommand. E.g., wb_todo_done already does this correctly, apply the same pattern to wb_todo, wb_query, wb_fin, wb_note, wb_manage, wb_dev_task, wb_vault, wb_archive.
• Document output schemas for all tools. Specify returned fields, types, and which IDs/references are included for chaining. E.g., list_todos should return [{ id, title, priority, due, status, tags }] with pagination (total, next_cursor).
• Add tool annotations: mark read-only tools with readOnlyHint=true; mark destructive tools (wb_todo_del) with destructiveHint=true; mark idempotent tools with idempotentHint=true. This enables agents to reason about safety.
• Add error handling guidance to descriptions. E.g., 'Returns 404 if todo not found, try search_todos() first. Returns 403 if no write permission, check user role.' Include retryable vs fatal classification.