Single tool 'eda_device_list' has a basic description but lacks critical schema documentation. No visible input parameter definitions, output schema, or structured response format in the provided source. The tool is described as 'static introspection' but no actual schema or parameter constraints are evident. Tool definition appears inferred rather than explicitly registered with full metadata. STDIO transport and minimal feature set further limit production readiness.

• Add explicit JSON Schema input definition to eda_device_list, even if empty ({}). Include parameter descriptions for any filters (e.g., device_type, category).
• Document output schema with typed fields: e.g., { devices: [{ name, type, tools: [{ name, description, params }] }], total_count }. This enables LLMs to extract device names and tool inventories.
• Expand description to 100-150 chars: 'Lists all available EDA devices (Yosys, OpenROAD, KLayout, etc.) and their exposed tools. Call this first to discover available synthesis, simulation, and hardware tools before invoking them.'
• Add error handling guidance: 'If no devices found, verify EDA_CONTAINER environment variable is set and the container is running. Returns empty list if container is unavailable.'
• Provide explicit tool registration code in bootstrap.mjs showing server.setRequestHandler(ListToolsRequestSchema, ...) with full schema and description inline.