ACP Patchbay exposes 6 tools with minimal parameter schemas and sparse descriptions. All tools have empty input schemas (no properties, no required fields), which violates the schema requirement. Descriptions are present but generic (10-80 chars), below the 50-200 char baseline for LLM-optimized docs. The request_user_input tool has a more detailed schema, but the other 5 are read-only queries with no parameters, this limits their utility and makes them appear incomplete. No output schemas are documented. Error handling and recovery guidance are absent. The tools are well-named (verb_noun pattern) but lack the depth needed for production-grade agent integration.

• Expand tool descriptions to 50 - 200 characters. Example: 'get_selection' → 'Returns the user's current editor selection: file path, line range, and selected text. Empty if nothing is selected. Use this to understand what code the user is working on.'
• Document output schemas for all tools. Specify the structure of each response (e.g., get_selection returns {file: string, startLine: number, endLine: number, text: string}).
• Add error handling guidance to each tool description. Example: 'If no file is open, returns {file: null, text: ""}. If diagnostics cannot be fetched, returns {errors: []} with a note in the response.'
• For request_user_input, clarify that 'properties' is an array of form field definitions, and document whether 'title' and 'description' are required or optional for each field.
• Consider adding tool annotations (readOnlyHint: true) to all 5 read-only tools to signal to agents that these calls are safe to retry and have no side effects.

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

• Relies on Stateful initialize / Mcp-Session-Id (removed; protocol is stateless) - make each request self-contained