Voice Access users will already have the function to "show labels" to see what the text alternative for that control is intended to be. Where a developer has neglected to add an accessible name for that control as a ContentDescription, Voice Access users can still say 'show numbers" to indicate the items in the screen that are interactions.

if you are working on this component, make sure the ContentDescription role is being used such as to label that icon, that should address your question.

Also don't just make up a name if there is already a design library for your app's icons such as the shopping trolley. It would be a bad user experience if in one place the shopping cart is labeled as "checkout" and somewhere else it's "buy" for assistive technology users. Keep in mind that for most labels this affects both speech and screen reader users, so including adequate content descriptions will help users with both motor and sight issues. Not to mention all the voice users that talk to their phone out of convenience that discover the ways Voice Access can be used to complement your voice assistant of choice.