en-quire provides 2 tools with documented schemas and descriptions, but lacks critical safety patterns and error-handling guidance. Tool names follow verb_noun convention (doc_append_section, text_append), but descriptions are moderately detailed without clear error recovery paths. Input schemas are present with type definitions and parameter descriptions, but lack enums for constrained inputs and do not document output structures. Security patterns for write operations are partially addressed via 'mode' parameter (write/propose) and 'if_match' ETags, but error responses and confirmation mechanisms are not visible in the provided source. The server supports Git-backed proposals and RBAC (evident from en-core dependencies), but these are not exposed as tool-level documentation. Missing: actionable error messages, batch operations, per-parameter validation guidance, and output schema documentation.

• Add explicit output schema to both tools. Minimum: { type: 'object', properties: { etag: { type: 'string', description: 'New ETag for subsequent writes' }, file: { type: 'string' }, branch?: { type: 'string', description: 'Git branch name if mode=propose' } } }
• Enhance error descriptions with recovery guidance. Example: 'if_match ETag mismatch → conflict: fetch fresh ETag via doc_read(file) and retry with updated if_match value.'
• Add enum constraint to 'mode' parameter in JSON Schema: { mode: { type: 'string', enum: ['write', 'propose'], description: '"write" applies immediately; "propose" creates a git branch for review.' } }
• Clarify when to use doc_append_section vs text_append in tool descriptions. Example: 'Use doc_append_section for Markdown documents with named sections; use text_append for plain text or when appending outside structured sections.'
• Add file path constraints: max length 255 chars, no leading '/', no '../' sequences. Document in parameter description.
• Add content size limits to description: 'Max 1MB per append. For larger content, split into multiple calls or consider bulk operations.'
• Implement dry-run support for both tools. Return diff preview without committing when mode='propose', enabling LLM confidence before applying changes.
• Add section parameter description clarification for doc_append_section: 'Must be an exact heading match (case-sensitive) or valid hierarchical path. Use doc_outline() first to discover valid section names.'
• Document message parameter as optional with sensible default: 'Commit message (default: "Update {file} section {section}" or "Append to {file}")'

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

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