6 tools with complete input schemas and descriptions, but quality varies significantly. Tool names follow verb_noun convention (awf_adopt, awf_get, awf_start, awf_initialize, awf_create). Descriptions range 50-150 chars, meeting baseline minimums. However, parameter descriptions are often generic ('Optional...'), and output schemas are not documented. awf_adopt_pull_request_monitor has 18 parameters with complex interdependencies (repo_url vs repo_slug vs pr_url, cursor_auto_mode incompatible with effort/model) that are under-documented. No error handling guidance, no recovery patterns, no output schema documentation across any tool.

• Document output schemas for all 6 tools. Specify returned fields, types, and which IDs/references are needed for chaining (e.g., workspace_id from awf_create_workspace for use in awf_adopt_pull_request_monitor).
• Add explicit parameter constraints in descriptions: 'Pass either repo_url+pr_number OR pr_url, not both.' 'cursor_auto_mode (Cursor only) is incompatible with effort or model parameters.'
• Add error recovery guidance to tool descriptions: 'If startup times out, verify Docker daemon is running and has sufficient disk space. Retry with timeout_seconds=300.'
• Replace generic 'Optional...' descriptions with actionable guidance: 'model: Override the default model for the selected agent (e.g., gpt-4o for codex). Omit to use agent defaults.'
• Add tool annotations: destructiveHint=true for awf_adopt_pull_request_monitor, awf_start_local_service, awf_initialize_project_profile (write_profile=true), awf_create_workspace; readOnlyHint=true for awf_get_setup_status, awf_get_client_integration_instructions.