Server has 7 tools with basic schemas and descriptions, but significant gaps prevent higher scoring. All tools have descriptions (10-100 chars, mostly adequate), and input schemas are present with Zod validation. However, parameter descriptions are sparse or missing entirely (e.g., 'operation' in apply_operation is just 'Structured operation object' with no guidance on required fields, structure, or valid values). Output schemas are not documented, callers cannot predict response structure. Error handling is minimal; no recovery guidance or actionable error messages visible. The 'operation' and 'operations' parameters accept generic z.record(z.string(), z.unknown()) with no schema validation, inviting hallucinated payloads. No tool annotations (readOnlyHint, destructiveHint, idempotentHint) despite clear risk levels (WRITE, IRREVERSIBLE). Session handle management is opaque, no guidance on handle lifecycle or cleanup. Batch tool (apply_operations) is good composition, but missing pagination/limits on list_parts.

• Add explicit JSON Schema definitions for 'operation' and 'operations' parameters. Define required fields (type, target, modified, etc.), valid operation types (insert, delete, replace, comment), and provide a schema example in the description.
• Document output schemas for all tools. E.g., open_docx returns {handle: string, path: string, parts: number}; list_parts returns {handle: string, parts: [{path: string, type: string}]}. Include in tool descriptions or a separate schema reference.
• Add tool annotations: mark write_part, apply_operation, apply_operations, save_docx with destructiveHint=true; mark open_docx, list_parts, read_part with readOnlyHint=true. Agents need to know which calls are safe to retry.
• Enhance parameter descriptions: specify valid partPath values (e.g., 'Path to OOXML part, e.g. word/document.xml, word/comments.xml, word/styles.xml'); document maxChars default and range; clarify author default ('defaults to "AI Agent" if omitted').
• Add error recovery guidance: 'If file not found, verify the path is absolute or relative to the working directory. If DOCX is invalid, ensure it is a valid Office Open XML file.' Include in tool descriptions or a separate error reference.

Inferred effective spec: 2025-06-18+.

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