diff --git a/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md b/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
index 9b73433867..fc733cc598 100644
--- a/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
+++ b/entity-framework/core/what-is-new/ef-core-10.0/breaking-changes.md
@@ -22,6 +22,7 @@ This page documents API and behavior changes that have the potential to break ex
 
 | **Breaking change**                                                                                             | **Impact** |
 |:--------------------------------------------------------------------------------------------------------------- | -----------|
+| [EF tools now require framework to be specified for multi-targeted projects](#ef-tools-multi-targeting)         | Medium     |
 | [Application Name is now injected into the connection string](#sqlserver-application-name)                      | Low        |
 | [SQL Server json data type used by default on Azure SQL and compatibility level 170](#sqlserver-json-data-type) | Low        |
 | [Parameterized collections now use multiple parameters by default](#parameterized-collections)                  | Low        |
@@ -31,6 +32,54 @@ This page documents API and behavior changes that have the potential to break ex
 | [IDiscriminatorPropertySetConvention signature changed](#discriminator-convention-signature)                    | Low        |
 | [IRelationalCommandDiagnosticsLogger methods add logCommandText parameter](#logger-logcommandtext)              | Low        |
 
+## Medium-impact changes
+
+<a name="ef-tools-multi-targeting"></a>
+
+### EF tools now require framework to be specified for multi-targeted projects
+
+[Tracking Issue #37230](https://github.com/dotnet/efcore/issues/37230)
+
+#### Old behavior
+
+Previously, the EF tools (dotnet-ef) could be used on projects targeting multiple frameworks without specifying which framework to use.
+
+#### New behavior
+
+Starting with EF Core 10.0, when running EF tools on a project that targets multiple frameworks (using `<TargetFrameworks>` instead of `<TargetFramework>`), you must explicitly specify which target framework to use with the `--framework` option. Without this option, the following error will be thrown:
+
+> The project targets multiple frameworks. Use the --framework option to specify which target framework to use.
+
+#### Why
+
+In EF Core 10, the tools started relying on the `ResolvePackageAssets` MSBuild task to get more accurate information about project dependencies. However, this task is not available if the project is targeting multiple target frameworks (TFMs). The solution requires users to select which framework should be used.
+
+#### Mitigations
+
+When running any EF tools command on a project that targets multiple frameworks, specify the target framework using the `--framework` option. For example:
+
+```bash
+dotnet ef migrations add MyMigration --framework net9.0
+```
+
+```bash
+dotnet ef database update --framework net9.0
+```
+
+```bash
+dotnet ef migrations script --framework net9.0
+```
+
+If your project file looks like this:
+
+```xml
+<PropertyGroup>
+  <TargetFrameworks>net8.0;net9.0</TargetFrameworks>
+</PropertyGroup>
+```
+
+You'll need to choose one of the frameworks (e.g., `net9.0`) when running the EF tools.
+
 ## Low-impact changes
 
 <a name="sqlserver-application-name"></a>