Single tool 'run_linear_pipeline' has critical definition gaps. Description is present (89 chars, within 10-1024 range) but lacks actionable context: does not explain WHEN to use it, what prerequisites exist, or what the state dictionary structure should be. Input schema present but parameters lack descriptions, 'state' and 'steps' have no guidance on expected format, constraints, or examples. No output schema documented. Tool name 'run_linear_pipeline' is generic and does not follow verb_noun pattern clearly (verb is implicit). No error handling guidance. No parameter validation rules stated. Fails 6 of 7 critical checks in Dimension 1.

• Add parameter descriptions: 'state' → 'Initial state dictionary (object) to be transformed. Keys are arbitrary; values can be any JSON type.' 'steps' → 'Array of transformation step names (strings) to execute sequentially. Each step must be registered in the workflow graph.'
• Document output schema explicitly: 'Returns {status: string (SUCCESS|ERROR), final_state: object (mutated state after all steps), trace?: array (optional execution trace)}.'
• Expand tool description to 150-200 chars: 'Execute a sequential pipeline of named state transformations. Each step receives the current state, applies a transformation, and returns a delta to merge. Use when you need to chain multiple operations on shared state. Prerequisites: all steps must be pre-registered in the workflow graph.'
• Add error handling guidance: 'If a step name is not registered, returns error with available step names. If state mutation fails, returns partial state and error details. Retry with corrected step names or validate state structure.'
• Rename tool to 'execute_transformation_pipeline' or 'apply_state_transformations' to follow verb_noun pattern and clarify intent.