Four tools with clear security-focused design and good descriptions (avg 156 chars). All tools have input schemas with typed parameters and descriptions. However, output schemas are not documented in the source code, and error handling lacks recovery guidance. Tool naming follows verb_noun convention well (dispatch_unit, dispatch_status, dispatch_result, dispatch_list). No tool annotations (readOnlyHint/destructiveHint) present. Composition is sound, each tool has one responsibility and chains naturally (dispatch_unit → dispatch_status/dispatch_result → dispatch_list). Security boundary is well-articulated in docstrings but not enforced via schema constraints (e.g., no enum for orguser/repo validation).

• Document output schemas for all four tools. E.g., dispatch_unit returns {handle: string, queued_at: ISO8601}; dispatch_status returns {handle, status: 'queued'|'running'|'done'|'failed', progress: int}; dispatch_result returns {handle, exit_code: int, detail: string}; dispatch_list returns {dispatches: [{handle, status, task_description}]}.
• Add tool annotations via FastMCP: @server.tool(name='dispatch_unit', description='...', annotations={'destructiveHint': True}). Mark dispatch_status, dispatch_result, dispatch_list with readOnlyHint=True.
• Enhance error messages with recovery paths. In _run(), catch DispatchError and map to specific messages: 'Unknown orguser: {orguser}. Available: {list_orgs()}' or 'Dispatch timed out. Retry with dispatch_status({handle}) or increase DISPATCH_TIMEOUT.'
• Expand dispatch_list description to ~100 chars: 'List all dispatches launched this session, including handle, status (queued/running/done/failed), and task description. Use to track in-flight work or find a handle to poll.'
• Add enum or pattern constraints to orguser and repo parameters in the schema. If allowlist is static, embed valid values; if dynamic, document the validation rule in the description.