Three tools with reasonable naming (verb_noun pattern) and descriptions (100-200 chars), but critical gaps in schema completeness and parameter documentation. download_content and download_multiple lack explicit parameter type definitions in visible code; list_downloads has minimal schema. No output schemas documented. Error handling guidance absent. Parameter descriptions exist but lack format constraints, ranges, or validation rules. No tool annotations (readOnlyHint/destructiveHint). Schemas appear inferred from JSON rather than explicitly defined in registration.

• Add explicit JSON Schema type/format/minLength/maxLength to all parameters. E.g., 'url': {type: 'string', format: 'uri', minLength: 10, maxLength: 2048}
• Document output schemas for each tool. E.g., download_content returns {type: 'object', properties: {file_path: {type: 'string'}, size_bytes: {type: 'integer'}, content_type: {type: 'string'}}}
• Add error recovery guidance to descriptions. E.g., 'If download fails due to network timeout, the tool will retry up to 3 times. If all retries fail, ask the user for an alternative URL.'
• Implement tool annotations in MCPAdapter._setup_handlers(). Add destructiveHint: true to download_content/download_multiple; readOnlyHint: true to list_downloads.
• Enhance parameter descriptions with format rules. E.g., 'pattern: Glob pattern (e.g., *.pdf, *.csv). Supports * and ? wildcards. Max 100 chars.'