Server has 28 tools with complete Zod schemas and descriptions in Spanish. Naming follows verb_noun convention (read_file, create_branch, list_sessions). Schemas are well-structured with type validation, enums, and constraints (e.g., branch name regex, UUID validation, max result limits). However, descriptions are brief (avg ~60 chars) and lack context on WHEN to use tools or dependencies between them. Parameter descriptions exist but are minimal. Output schemas are defined in Zod but not documented in tool registration. Error handling is present but recovery guidance is sparse. No tool annotations (readOnlyHint/destructiveHint) despite clear risk levels. Spanish descriptions reduce LLM clarity for English-speaking agents.

• Translate all tool descriptions and parameter descriptions to English. Use 50-200 character descriptions that state WHAT the tool does, WHEN to use it, and any prerequisites. Example: 'Reads a file from the workspace. Use this after search_codebase to fetch full content. Returns file path, extension, size, and content.'
• Add tool annotations to the MCP tool registration: readOnlyHint=true for read_* and list_* tools; destructiveHint=true for commit_changes, write_file_patch; idempotentHint=true for tools that can be safely retried.
• Document output schemas in tool registration. For each tool, add an 'outputSchema' field describing the response structure. Example for git_status: '{isGitRepository: boolean, currentBranch: string|null, stagedFiles: string[], modifiedFiles: string[], untrackedFiles: string[]}'.
• Add recovery guidance to error scenarios. In read_file description, add: 'If file not found, try search_codebase(query) to locate it, then read_file(path).' In commit_changes, explain how to obtain proposalId via list_pending_proposals().
• Reduce required parameters by providing smart defaults. E.g., sessionId and proposalId in commit_changes and write_file_patch should be optional with clear fallback behavior documented.

Inferred effective spec: 2025-06-18+.

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