Hatchdoor exposes 40 HTTP handlers as MCP tools but lacks critical definition quality. Tool names use inconsistent patterns (_handler suffix, no clear verb-noun structure). Descriptions are present but extremely terse (8-30 chars), far below the 50-200 char baseline for LLM optimization. Input schemas are either missing entirely or minimal (only vault_id visible for edit_vault; others inferred from handler names). No parameter descriptions, no output schemas documented, no error recovery guidance. The server appears to be a web/vault management API wrapped as MCP tools without proper tool design. Composition is poor: many tools operate on the same vault resource but lack clear differentiation (e.g., refresh_vault_handler vs sync_vault_handler vs retry_vault_handler). No evidence of idempotency, pagination, or structured output design.

• Remove '_handler' suffix from all 38 tool names. Rename to verb_noun format: create_vault, list_vaults, get_settings, patch_settings, etc. This matches LLM expectations and reduces cognitive load.
• Expand all descriptions to 50-200 characters. For example: 'Create a new vault' → 'Create a new vault to store and organize markdown notes. Specify a name and optional remote source URL for syncing.' Include WHEN to use the tool and what it returns.
• Add complete input schemas for all 40 tools. For vault-scoped tools, include vault_id (required, string). For note operations, include vault_id and note_id. For search/list tools, add limit, offset/cursor, and filter parameters with type definitions and descriptions.
• Document output schemas for all tools. Specify what fields are returned (e.g., vault_id, vault_name, created_at, status). For list tools, include total_count and next_cursor for pagination. For note operations, return note_id, vault_id, and path so downstream tools can chain.
• Clarify overlapping tool semantics. Add descriptions explaining: refresh_vault_handler (re-index local vault), sync_vault_handler (pull from remote source), retry_vault_handler (retry failed sync). Similarly, distinguish move_note from move_rename_note. Add parameter descriptions showing which parameters are required for each operation.