MCPfinder has 5 tools with clear verb-noun naming (search_, get_, add_, remove_, list_). All tools have descriptions (avg 95 chars, within baseline 34-392). Input schemas are present and use Zod validation with type definitions. However, parameter descriptions are sparse or missing in several tools, output schemas are not documented, and error handling lacks recovery guidance. The add_mcp_server_config tool has complex nested schemas but minimal guidance on when to use optional fields. No tool annotations (readOnlyHint/destructiveHint) despite clear risk profiles (WRITE vs READ_ONLY).

• Document output schemas for all tools. E.g., search_mcp_servers should return {servers: [{id, name, description, url, tags}], total_count, next_cursor?} instead of free-text blocks.
• Add destructiveHint and readOnlyHint annotations to tool definitions. Mark add_mcp_server_config and remove_mcp_server_config with destructiveHint:true to signal to agents that these modify state.
• Expand parameter descriptions with search semantics. For search_mcp_servers, clarify: 'Search across server name, description, and tags. Case-insensitive. Multiple keywords use AND logic. Max 100 results returned.'
• Add recovery guidance to error responses. E.g., 'Server not found. Try search_mcp_servers() with partial name or browse available tags.' instead of bare 'Failed to fetch'.
• Document the conditional logic in add_mcp_server_config. Explain: 'If mcp_definition.command is omitted, defaults will be fetched from registry. Provide env and workingDirectory only if non-standard.'