Machineuse exposes 12 tools with severe definition gaps. Most tools lack proper parameter descriptions and input validation. Tool schemas are minimal or missing entirely. Descriptions are present but generic. The server appears to be a container management system, but tool definitions do not follow agentic tool patterns, they read more like internal API endpoints than LLM-friendly tool interfaces. Critical issues: (1) create_instance and list_instances have empty required schemas with no input parameters documented; (2) Tools like register_handler, register_topic_handler, start_reply_server, start_subscriber, start_pull_server expose internal messaging infrastructure (NNG/ZMQ patterns) rather than user-facing abstractions; (3) Descriptions lack clarity on when to use each tool vs alternatives; (4) No error handling guidance; (5) Parameter descriptions are sparse or missing; (6) No pagination, limits, or output schema documentation; (7) Several tools (register_handler, register_topic_handler) accept complex objects ('MessageHandler object') without defining the expected schema.

• Define explicit input schemas for create_instance and list_instances. Add properties like instance_name, base_port, memory_limit, cpu_limit (with type, description, and constraints). Add required fields if any are mandatory.
• Document the InstanceCreationRequest schema for queue_instance_creation. Define its properties, required fields, and type constraints. If it mirrors create_instance, state that explicitly.
• Clarify when to use create_instance vs queue_instance_creation. Add descriptions like 'Use create_instance for immediate synchronous creation; use queue_instance_creation to defer creation via task queue for load balancing.'
• Add output schema documentation to all list/get tools. E.g., 'list_instances returns {instances: [{id, name, status, cpu_percent, memory_mb, ...}], total: int, next_cursor?: string}'.
• Implement pagination for list_instances. Add optional parameters: offset (int, default 0), limit (int, default 20, max 100), and return total_count or next_cursor in response.
• Move credential handling out of tool parameters. For authenticate_instance_key, use server-side Bearer token injection (from request headers or environment) instead of passing credentials as a tool parameter.
• Add error recovery guidance to each tool description. E.g., 'If instance not found, call list_instances to verify the ID; if still not found, check that the instance has not expired (older than 30 days).'
• Add a confirmation pattern or dry-run option to delete_instance. Provide a 'confirm_delete_instance' tool or a 'dry_run' boolean parameter, with explicit warnings in the description.