Single tool with minimal schema and generic description. Tool name 'validate_libvirt_xml' is clear and verb-based, but description (67 chars) lacks context on when to use it, what it returns, or error recovery paths. Input schema present but sparse: only one parameter with minimal description. No output schema documented. Error handling exists in code but not surfaced in tool definition. No parameter constraints, enums, or format guidance. Follows basic tool structure but falls short of production quality across naming, description depth, and schema completeness.

• Expand tool description to 150 - 250 chars: explain what validation checks are performed, when to call it (e.g., before deploying a VM), what a successful response contains, and what each error category means.
• Document output schema explicitly: 'Returns a string message indicating success and detected object type (e.g., "XML validation successful. Detected object type: \'<domain>\'."). On failure, raises McpError with INVALID_PARAMS or INTERNAL_ERROR.'
• Add constraints to xml_content parameter: 'XML string (UTF-8 encoded, max 10 MB). Must be well-formed XML with a root element matching a known Libvirt object type (domain, network, pool, etc.).'
• Document error recovery in description: 'If validation fails with LibvirtXmlSchemaError, the XML structure is invalid for the detected object type. Review the error message for specific schema violations. If schema is not found, ensure the Libvirt version matches the bundled RNG schemas.'
• Consider adding a companion tool (e.g., list_libvirt_schemas or describe_libvirt_object_type) to help agents discover valid XML structures before validation.

Inferred effective spec: <=2025-11-25.

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry