Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already declare readOnly, idempotent, non-destructive, closed-world behavior, so the safety profile is covered. The description adds genuinely new decision-relevant context beyond that: the call is free (no credit cost), and the catalog carries 'new' merge fields, which matters to an agent deciding whether to refresh state. It does not explain per-section behavior, but the bar is lower given full annotation coverage.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.