Server has 4 tools with basic schemas and descriptions, but significant gaps in parameter documentation, error handling, and output structure. All tools have descriptions (10-100 chars), but most are generic. Schemas present but incomplete: 'get-all-templates' and 'get-specific-template' have empty input schemas; 'complete-template' lacks descriptions for 'templateId' and 'values' parameters; 'generate-invoice' has nested schema but no output schema documented. Error handling is minimal, all tools catch errors and return generic 'Error fetching templates' or 'Error generating invoice' messages without recovery guidance. No tool annotations (readOnlyHint, destructiveHint). Naming is verb-noun compliant but generic ('get-*', 'complete-*', 'generate-*'). No pagination, no result limits, no chaining IDs in responses.

• Add descriptions to all parameters. 'templateId' should describe format/constraints; 'values' should explain key-value structure and required keys.
• Document output schemas for all tools. E.g., 'Returns array of {id, name, description}' for get-all-templates; '{success, filePath, error}' for generate-invoice.
• Replace generic error messages with actionable guidance. E.g., 'Failed to fetch templates from http://10.0.0.5:3000. Verify server is running and accessible. Retry or contact admin.'
• Add tool annotations: readOnlyHint=true for get-* tools; destructiveHint=true for complete-template and generate-invoice (they write files).
• Add input validation and return specific constraint violations. E.g., 'Invalid responseType: got "xml", must be "json" or "pdf"' instead of generic error.