Single tool with critical definition gaps. Tool name 'minimize_failure' lacks action verb clarity (should be 'minimize_*' or 'reduce_*'). Input schema present but incomplete: 'elements' parameter has no description (only type:array), violating the requirement that every parameter needs a description. Output schema entirely undocumented, LLMs cannot plan downstream calls or extract results. Tool description is minimal (11 words, 67 chars) and lacks WHEN/WHY context. No error handling guidance. No parameter constraints (enums, ranges, formats). Fails multiple critical checks from pattern:tool and pattern:tool-description.

• Add description to 'elements' parameter: 'List of items to minimize (e.g., lines of code, tokens, characters). Order is preserved. Must trigger failure when passed to test function.'
• Document output schema in tool description or as a separate schema block: 'Returns object with minimal_elements (array), initial_size (int), minimized_size (int), steps (int), reduction_percentage (string percentage).'
• Expand tool description to 100-150 chars: 'Minimize a failing input list to the smallest subset that still reproduces the failure using the ddmin algorithm. Requires a test function that returns True when failure reproduces. Returns minimal elements, reduction percentage, and iteration count.'
• Add parameter 'target_elements' description: 'Elements that must be present in the result to simulate the failing condition. Used to construct the test function internally.'
• Implement structured error responses: catch ValueError and return {error: 'Input elements do not trigger failure. Verify test_func returns True for the full input list.', recovery: 'Check that target_elements are actually present in elements.'}