Agent Designer provides 7 tools with mixed quality. Four bridge tools (agy_bridge, claude_bridge, codex_bridge, grok_bridge) have well-structured schemas with detailed parameter descriptions (8-12 params each, all typed). Three workflow tools (create_plan, create_issues, list_plans) have simpler but adequate schemas. However, tool descriptions are present but relatively brief (50-150 chars), lacking the depth and context LLMs need for confident tool selection. No output schemas are documented, callers cannot know what fields to expect from responses, violating the output-schema requirement. Error handling exists in code but is not surfaced in tool metadata. One critical issue: tool names use underscores (agy_bridge) rather than clear verb_noun patterns that convey action (run_agy, invoke_agy would be clearer). The server supports session persistence via SESSION_ID parameters across multiple tools, which is good for multi-turn continuity, but this is not explicitly documented in tool descriptions as a feature.

• Document output schemas for all 7 tools in the MCP server metadata. Include field names, types, and whether pagination is supported. E.g., agy_bridge should declare returns {output: string, stderr: string, exit_code: number, session_id: string, timed_out: boolean}.
• Rename bridge tools to verb_noun format: 'run_agy', 'run_claude', 'run_codex', 'run_grok' or 'invoke_agy_print', 'invoke_claude_print' to make the action obvious. Current names conflate the CLI tool with the MCP tool.
• Expand tool descriptions to 100-200 chars. Add context: 'Invoke Antigravity CLI in headless print mode (--print) to execute a prompt against the specified workspace. Supports session resumption via SESSION_ID for multi-turn continuity. Use this when you need Antigravity's code generation or analysis capabilities.'
• Document that SESSION_ID parameter enables multi-turn conversations by resuming prior sessions. Add guidance: 'Leave empty for new session; pass returned SESSION_ID from prior calls to continue context.'
• Formalize timeout and sandbox constraints. Replace print_timeout's example-based description with either an enum (predefined options) or a regex pattern constraint. Same for permission_mode values, ensure all enums are documented in descriptions.
• Add error handling guidance to tool descriptions. E.g., 'Returns non-zero exit_code and stderr on failure. Check stderr for permission errors, timeouts, or invalid prompts. If timed_out=true, SESSION_ID is preserved for retry.'
• Document the workspace path parameter behavior consistently across all 4 bridge tools. State whether it must exist, whether relative paths are supported, and what happens if not provided.