Single tool with partial schema definition. Tool name 'rbx_apply_patch_safe' uses underscore prefix (non-standard) and lacks clear verb-noun structure. Description is adequate (73 chars) but generic. Input schema present with 5 parameters, all typed and described, but output schema is completely undocumented, critical gap for LLM planning. No error handling guidance, no recovery paths, no per-item success/failure reporting for array operations. Parameter 'operations' accepts array with no item schema constraints, inviting malformed patches. Dry-run support is good (idempotent pattern), but undo mechanism lacks documentation of what happens on failure.

• Document the complete output schema: What fields does the response contain? Include patch_id, applied_count, failed_operations (with per-item error details), and any state changes.
• Rename tool to 'apply_roblox_patch' and restructure description to answer: WHAT (applies safe mutations), WHEN (preview with dry_run=true first), WHAT IT RETURNS (patch_id, results).
• Define 'operations' array item schema with enum for operation type (create|update|delete|reparent) and required fields per type. Example: {type: 'create', parent_path: string, class_name: string, properties: object}.
• Add error handling section to description: 'Returns error_code (INVALID_OPERATION, PERMISSION_DENIED, ROLLBACK_FAILED) with actionable message. Retryable errors include ROLLBACK_FAILED; non-retryable include INVALID_OPERATION.'
• Document undo_patch_id behavior: 'Reverses a previously applied patch. Idempotent, calling twice with same patch_id is safe. Returns success or UNDO_NOT_FOUND if patch_id invalid.'