Single tool 'emailrecon_scan' has a basic description (67 chars) but critically lacks parameter descriptions. The input schema defines 'target' as a string with no description explaining what format is expected (email address, domain, file path?). No output schema is documented, the tool returns JSON but the structure is not formally specified. The description is adequate but parameter documentation is absent, violating the requirement that every parameter needs a description. No error handling guidance is provided.

• Add description to 'target' parameter: 'Email address to analyze (e.g., [email protected]). Tool will perform OSINT checks including breach hints, MX records, SPF/DMARC posture.'
• Document output schema in tool description or as a separate schema block: 'Returns JSON object with fields: email (object with normalized, valid_syntax, local_part, domain, flags), domain (object with mx_records, spf_policy, dmarc_policy, mta_sts_hint), breach_hints (array), score (integer).'
• Add error handling guidance: 'If email syntax is invalid, tool returns valid_syntax=false. If domain lookups fail, tool returns empty mx_records and null policies. Check the returned email.valid_syntax field before interpreting domain results.'
• Rename tool to 'scan_email_osint' or 'analyze_email_posture' to clarify the specific reconnaissance domain and expected output type.
• Add parameter constraints: specify valid email format (RFC 5322 subset), max length, and whether internationalized domains are supported.