Best practice for including a dependency in a 3rd party plugin?

I’m trying to make my jar file available to a 3rd party plugin. The approach I’ve found to work is to add

buildscript {
    dependencies {
        classpath ("my-group-id:my-artifact-id:version")
    }
}

to the top-level build.gradle file.

My question is, is this the best way to configure this? Adding it to the buildscript doesn’t sound the most obvious place for when someone will come to look at this at a later date.