Orchestra provides a single tool (bash_tool) with a clear, production-focused description and well-structured input schema. The tool name follows verb_noun convention (bash_tool), and the description explicitly warns about user approval requirements and local execution context. However, the tool lacks critical patterns: no error recovery guidance, no dry-run/confirmation mechanism for an irreversible operation (bash execution), no output schema documentation, and no rate limiting or timeout guidance despite supporting configurable timeout_ms. The input schema is properly typed with descriptions, but the tool is high-risk (IRREVERSIBLE) and should have stronger safety guardrails.

• Document the output schema explicitly: return object with {exit_code: integer, stdout: string, stderr: string, duration_ms: integer}. This enables LLMs to parse results and detect failures.
• Add error recovery guidance to the description: 'If exit code is non-zero, the command failed. Check stderr for the error message. Use a simpler command or verify the working_directory exists.' Provide actionable next steps.
• Implement dry-run support by adding an optional 'dry_run: boolean' parameter. When true, return the command that would execute without actually running it. This prevents accidental destructive operations.
• Document timeout behavior: 'If the command exceeds timeout_ms, execution is killed and an error is returned. Increase timeout_ms for long-running operations (max: 300000ms = 5 minutes).'
• Add rate limiting guidance: document that the tool enforces per-minute rate limits to prevent resource exhaustion. Include retry-after header interpretation in error responses.
• Clarify the approval mechanism in the tool description and confirm it is implemented server-side. If approval is manual/out-of-band, document how LLMs and users coordinate this (e.g., via tool annotations or confirmation callbacks).