TerseSharp exposes 34 tools for C# development (code navigation, refactoring, Razor component editing, package management). Critical gaps: NO visible input schemas in source code (ToolProfile.cs, ToolGuard.cs show tool registration but schema definitions are not present in provided excerpts). Tool descriptions are sparse or missing entirely, most tools listed without docstrings. Parameter descriptions absent. Error handling exists (ToolArgumentFilter.cs shows structured error responses with remediation hints), but tool-level documentation is severely underdeveloped. Naming is generally clear (verb_noun pattern: load_workspace, get_file_outline, replace_symbol), but lack of schema visibility and descriptions prevents LLMs from understanding parameter constraints and output structure. No evidence of output schema documentation.

• Add comprehensive input schemas to all 34 tools. Define parameter types (string, number, boolean, array), required fields, enums for constrained values (e.g., razor_find kind=component|element), and min/max for numeric params. Reference: pattern:constrained-input.
• Write tool descriptions (50 - 200 chars) for all tools. Example: 'get_file_outline: Returns the hierarchical structure of symbols (classes, methods, properties) in a C# file. Use this to understand code organization before refactoring.' Include WHEN to use and WHAT it returns.
• Document every parameter with type, constraint, and example. E.g., 'glob (string, required): File glob pattern (e.g., src/**/*.cs). Supports * and ** wildcards.' Avoid bare parameter names.
• Document output schemas. Specify returned fields, types, and pagination. E.g., 'Returns array of {name: string, kind: string, line: number, column: number}. Capped at 100 results; use offset/limit for pagination.'
• Add destructiveHint and idempotentHint annotations to write/delete tools. Implement dry-run parameters (dryRun=true) for razor_* and package_* tools to enable safe preview before commit. Reference: pattern:confirmation-request.