Six tools with clear verb-noun naming (server_tool_ls, profile_tool_allow, etc.) and consistent structure. All have descriptions (avg ~80 chars) and input schemas with typed parameters. However, descriptions are terse and lack WHEN/WHY guidance. Parameter descriptions are minimal (often single phrases). No output schemas documented. Error handling and recovery guidance absent. Missing idempotency hints on write operations. No examples of chaining IDs across tool responses.

• Document output schemas for all tools. E.g., server_tool_ls should specify: returns array of {name: string, description: string, risk: enum, blocked: boolean, ...}, with pagination if applicable.
• Expand descriptions to 100 - 150 chars with WHEN/WHY guidance. E.g., 'List all tools from a server or search by name. Call this first to discover available tools before inspecting or allowing specific ones.'
• Add parameter descriptions that explain defaults and discovery. E.g., 'server: Optional server name. If omitted, lists tools from all servers. Use server_list to discover valid names.'
• Add idempotency and side-effect hints to write tools. E.g., 'Calling this multiple times with the same parameters is safe and idempotent. Changes take effect immediately.'
• Document error cases and recovery. E.g., 'If server not found, returns error with list of available servers. If tool is blocked, response includes reason (global rule, profile rule, or pending approval).' Add a recovery-guide pattern.