Zero's tool definitions are severely underdeveloped. Only 2 of 7 tools have visible input schemas (apply_patch, read_file); the remaining 5 lack documented schemas entirely. Descriptions are minimal (10-50 chars) and lack actionable context. No parameter descriptions are present. Tool definitions appear inferred from test code rather than formally registered. No output schemas documented. Error handling and recovery guidance absent. This server does not meet baseline quality standards for production agent tooling.

• Add formal tool registration with complete JSON Schema for all 7 tools. Include type, description, and constraints for every parameter. Example: apply_patch should document 'value' as string with format 'unified-diff' and max length.
• Expand all tool descriptions to 100-200 characters following the pattern: 'Applies unified diff patches to files in the workspace. Use after analyzing file changes. Returns success status and list of modified files.' Include WHEN to use and WHAT it returns.
• Add parameter descriptions for apply_patch.value and read_file parameters. E.g., 'value: Patch content in unified diff format (RFC 3881). Max 1MB. Must contain valid hunk headers.'
• Document output schemas for all tools. E.g., apply_patch returns {status: 'ok'|'error', files_modified: string[], error_message?: string}. This enables LLM planning.
• Add error handling guidance. E.g., 'If patch fails to apply, call grep to verify file content matches expected state, then retry with corrected patch.' Per pattern:recovery-guide.