Argus MCP server has severe definition quality gaps. Tool descriptions are minimal (10-50 chars, well below the 50-200 char baseline for LLM-optimized descriptions). Most tools lack visible input schemas in the source code, only 3 of 8 tools show explicit schema definitions. Parameter descriptions are generic or missing. No output schemas documented. Error handling is absent. The server appears to expose design analysis capabilities but fails to provide the structured, self-documenting interface required for reliable agent integration.

• Expand tool descriptions to 50-200 characters. Example: 'design.score: Analyze a page snapshot and return a design quality score (0-100) across 6 categories: typography, spacing, color, contrast, alignment, and accessibility. Requires a valid PageSnapshot object from design.inspect or your browser extension.'
• Document output schemas for all tools. Specify what fields each tool returns (e.g., design.score returns {score: number, categories: {[key]: number}, passed: boolean, violations: string[]}).
• Add parameter descriptions that explain format and constraints. Example: 'snapshot: A PageSnapshot object with required fields: {elements: Element[], styles: CSSMap, viewport: {width, height}, url: string}. Obtain via design.inspect or browser extension.'
• Implement error handling with recovery guidance. Example: 'If snapshot validation fails, ensure it includes all required fields. Call design.inspect to generate a valid snapshot, or use the browser extension to capture the current page.'
• Add input schemas to design.inspect, design.apply, and design.doctor. Even if they accept no parameters or minimal parameters, declare this explicitly in the schema (e.g., {type: 'object', properties: {}, required: []}).