Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare destructiveHint=true, readOnlyHint=false, idempotentHint=false and openWorldHint=true, so the safety profile is known. The description adds genuinely new context: no outreach is sent, and edits/deletion have downstream consequences on already-printed codes -- which is exactly the side-effect detail annotations cannot convey. It omits, however, that update/delete require an explicit user approval gate (only stated in the schema) and does not clarify whether deletion is recoverable.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.