Single tool 'write-text' has a clear verb-noun name and proper input schema with enum constraints on 'mode'. However, the tool description is minimal (34 chars, below the 50-200 char LLM-optimized range), and parameter descriptions lack actionable detail about format/constraints. The 'text' parameter description is generic ('Content to write to Textwell') without guidance on length limits, encoding, or special character handling. No output schema is documented. Error handling exists but lacks recovery guidance. Overall definition quality is below median due to sparse descriptions and missing output documentation.

• Expand tool description to 80 - 150 characters: 'Write or insert text into the Textwell application. Use mode=replace to overwrite all content, mode=insert to place text at the cursor, or mode=add to append at the end. Returns success confirmation.'
• Add constraints to 'text' parameter: 'Plain text content to write (max 100,000 characters). Special characters are URL-encoded automatically. Do not pre-encode.'
• Document output schema explicitly: 'Returns {type: "text", text: "Text [mode] completed"} on success.'
• Enhance error messages with recovery hints: 'Textwell write failed: [reason]. Ensure Textwell app is running and accessible. Retry or check app logs.'
• Add a note on idempotency: 'Calling this tool twice with the same text and mode is safe, the second call will produce the same result as the first.'

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

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