Single tool with minimal schema and generic description. Input schema is empty object (no parameters defined), violating the requirement that every parameter needs a description and type. Description is present but generic (79 chars), lacking actionable context about when/why to use the tool or what it returns. No output schema documented. No error handling guidance. Tool name 'check_workflows' is acceptable (verb_noun pattern) but lacks specificity about what 'check' entails.

• Define input schema with at least one optional parameter (e.g., 'include_recent_errors: bool' or 'limit: int') with type and description. Even if the tool takes no required inputs, document the schema structure.
• Expand description to 150-250 chars: 'Reviews all workflows in the n8n instance and reports their status. Returns total count, active/inactive breakdown, and identifies workflows with recent execution errors. Call this first to assess workflow health before investigating specific failures.'
• Document output schema in code comments or docstring: 'Returns {total: int, active: int, inactive: int, workflows_with_errors: [{id, name, last_error_time, error_message}]}'.
• Add error handling: catch httpx.HTTPError, timeout, and JSON decode errors. Return structured error with recovery hint: 'Failed to fetch workflows: {reason}. Verify N8N_BASE_URL and N8N_API_KEY environment variables are set correctly.'
• Implement pagination or result limits. If n8n returns 1000+ workflows, cap at 50 and document in description: 'Returns up to 50 workflows; use pagination for larger instances.'

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

• Relies on Logging (deprecated) - log to stderr or use OpenTelemetry