Four tools with complete input schemas and descriptions, but significant gaps in parameter documentation and output schema clarity. All tools have descriptions (10-100+ chars), but 3 of 4 lack descriptions for nested object properties. workflow.next_step has a complex nested schema with undocumented artifact and finding structures. No output schemas documented. Error handling is absent, tools do not guide recovery or categorize failures. Parameter descriptions exist but lack format constraints, ranges, or validation rules. Naming follows verb_noun pattern (workflow.*, knowledge.*) but lacks clarity on side effects and prerequisites.

• Document output schemas for all four tools. Specify what fields are returned, their types, and which are required. E.g., workflow.start should document whether it returns execution_id, status, initial_step, etc.
• Add descriptions to all nested object properties in workflow.next_step artifacts and findings. For each enum (type, scope, category, severity), explain what each value means and when to use it.
• Add error handling guidance: 'If token is invalid or expired, the workflow cannot continue, ask the user to restart. If a finding fails validation, check that scope=project requires project_id.'
• Clarify side effects in tool descriptions. workflow.next_step should state 'This persists findings to the knowledge base and advances the workflow state, it is not idempotent and should not be retried without checking state first.'
• Add format constraints to parameters: token (e.g., 'UUID or alphanumeric string'), project_id (e.g., 'positive integer'), severity (e.g., 'info=informational, low=minor issue, medium=moderate risk, high=significant risk, critical=blocks workflow').