Clarify Tag applied_at/applied_by are only present in tagging operations

[anubhav-intercom]

Why?

Customers report confusion because the Tag schema on the docs page shows applied_at and applied_by fields, but these are absent from direct tag lookups (GET /tags, GET /tags/{id}). These fields are only populated when a tag is returned as part of a tagging operation on a contact, conversation, or ticket — the tag schema is used by attach/detach endpoints, while tag_basic (without these fields) is used by direct lookups.

• https://github.com/intercom/intercom/issues/283507

How?

Updates the applied_at and applied_by descriptions in the tag component schema across all API versions to clarify they are context-dependent. No schema structure change — just improved descriptions.

Note: This change needs to be manually synced to intercom/developer-docs after merge (the OpenAPI specs are copied manually per the developer-docs README).

_{Generated with Claude Code}

[ellicenelson]

Correct fix!

Nit: For consistency you could probably use the same short clarification for both descriptions

e.g."Only present when the tag is returned as part of a tagging operation on a contact, conversation, or ticket." append on both applied_at and applied_by, instead of verbose "Only present when the tag is returned as part of a tagging operation on a contact, conversation, or ticket. Not included in direct tag lookups (GET /tags or GET /tags/{id})."