Currently, any AWS Secret in Jenkins has the name "AWS Secrets Manager secret." This is not a major issue in the credentials browser or accessing in a pipeline script, as the credential ID is unique – however, in the "Configure System" page, many plugins use the names rather than the ID to choose these secrets from the dropdown (see images)

The solution that I will experiment with is to source the credential name from the description field attached to the secret in AWS, however, using the ID as the description instead would work well.