Two tools with basic schemas and minimal descriptions. create_patch has a 67-char description (below baseline 194 chars); apply_patch_fuzzy has 65 chars. No error handling guidance, no output schema documentation, no parameter constraints (e.g., max_drift range). Naming is verb-forward (create_, apply_) but descriptions do not explain WHEN to use each tool or what they return. Parameter 'max_drift' lacks bounds or rationale. No mention of idempotency, side effects, or recovery paths.

• Add 100 - 150 char descriptions to both tools. Example for create_patch: 'Generate a unified diff patch comparing original and modified code. Use this to create patches for version control or code review. Returns a standard unified diff string with context lines.'
• Add descriptions to all parameters. Example: 'original_text (string): The original source code before modifications. Can be any length; newlines are preserved.' 'max_drift (integer): Maximum line offset tolerance when matching hunks (1 - 50). Higher values tolerate more line drift but risk incorrect matches.'
• Document output schemas in tool descriptions. Example: 'Returns {status: "success"|"conflicted", applied_hunks: int, total_hunks: int, conflicts: [{hunk_header, reason}], patched_text: string}'
• Add parameter constraints to schema. Set max_drift with minimum: 1, maximum: 50 in the JSON Schema properties.
• Clarify error recovery in apply_patch_fuzzy description: 'If conflicts occur, the response includes a conflicts array with hunk headers and reasons. Retry with a higher max_drift, or manually resolve conflicts.'