The server provides 7 well-named antenna design tools with clear action verbs (create, list, get, simulate, update, delete). All tools have descriptions present. Schemas are visible in the source code with proper type definitions and enums for antenna types and ground types. However, several parameter descriptions are minimal (e.g., 'ID of the antenna to retrieve' lacks format guidance), and output schemas are not formally documented in the code. Error handling and recovery guidance are not evident. The 'parameters' field in create_antenna accepts an object with 'Type-specific parameters' but lacks a formal schema for what those parameters should contain, making it difficult for LLMs to construct valid input. Most tools follow good naming conventions (verb_noun), but descriptions average ~50-80 characters, which is short of the 194-char baseline for production tools. No descriptions explain when to use one tool vs. another (e.g., when to use simulate_antenna vs. get_nec2_input). Security considerations like credential injection or rate limiting are not mentioned.

• Expand each tool description to 100-200 characters. Include what it does, when to use it (vs. similar tools), and what it returns. Example: 'Simulate antenna performance across a frequency range using NEC2 method of moments. Returns radiation patterns, gain, and feedpoint impedance. Use this after create_antenna to validate a design; use get_nec2_input if you only need the raw NEC2 code without running the solver.'
• For create_antenna, replace 'Type-specific parameters (height_m, num_directors, etc.)' with a formal nested schema. Define antenna_specific_params as an object with conditional properties: if antenna_type='yagi', num_directors (integer, 2-20) and boom_length_m (float) are required; if antenna_type='dipole', height_m is required, etc.
• Document all output schemas. For each tool, add a 'Returns' section in the docstring with field types and meanings. Example for create_antenna: 'Returns {antenna_id: string (UUID), antenna_type: string, frequency_mhz: number, created_at: ISO 8601 string, estimated_gain_dbi: number | null}'.
• Add error handling documentation. For each tool, describe expected failures and recovery. Example: 'If antenna_id is not found, returns error 'antenna_not_found'. Call list_antennas() to see available designs. If NEC2 simulation times out (>60s), reduce freq_steps or increase freq_start/freq_end range.'
• Add range and format constraints to all numeric and string parameters. Example: frequency_mhz should be 'Operating frequency in MHz (1.0 - 1000.0)'; antenna_id should be 'UUID format (e.g., 550e8400-e29b-41d4-a716-446655440000)'.