Revvy provides 5 well-named, read-only tools with clear descriptions (avg 156 chars, within baseline 194). All tools have complete input schemas with proper types and descriptions. However, output schemas are not documented, LLMs cannot predict return structure for chaining. Error handling is absent; no guidance on recovery or retryability. Tool descriptions lack dependency hints (e.g., 'call listChangedFiles first'). searchSymbol includes performance guidance (good), but other tools lack similar context. No tool annotations (readOnlyHint present implicitly via Risk field, but not in schema). Overall solid naming and parameter quality, but incomplete schema documentation and missing error patterns limit production readiness.

• Document output schemas for all tools. Example for listChangedFiles: 'Returns {files: [{path: string, status: string}], total: number}'. This enables LLM planning and chaining.
• Add error recovery guidance to descriptions. E.g., readFile: 'If file not found, call listWorkspaceFiles(glob="**/*") to verify the path exists.'
• Implement tool annotations in schema: add readOnlyHint: true to all tools (already safe, but make it explicit for client-side enforcement).
• Enhance listWorkspaceFiles description with glob syntax examples and performance note: 'Use specific globs (e.g., "src/**/*.ts") for large repos; unscoped "**/*" may be slow.'
• Add dependency hints to readFile and getFileDiff: 'Typically called after listChangedFiles() to identify which files to inspect.'

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

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