The choice between `@Attribute` and `@Input` depends on the use case and the nature of the data you are working with in your Angular directive.

Here are some considerations:

1. **Immutability of Attributes:**

- `@Attribute` provides a read-only view of an attribute value as a string. It reflects the initial value of the attribute at the time the element is created. Once set, it doesn't change even if the attribute value changes later.

- `@Input` is a more flexible way to handle dynamic changes to the property values as it allows two-way binding and supports both property and attribute binding.

2. **Type of Data:**

- If the data you are working with is simple and can be represented as a string (like boolean values 'true' or 'false' for an attribute), then using `@Attribute` might be more straightforward.

- If you need to work with more complex types, or if you want to support two-way binding, then `@Input` is a better choice.

3. **Binding Flexibility:**

- `@Attribute` is mainly for reading static values of an attribute at the time of component instantiation.

- `@Input` allows for more dynamic binding, as it can be updated through property binding in templates, and changes to the property are reflected in the component.

In the context of your example, if the `enabled` attribute is meant to be static and not change dynamically during the component lifecycle, using `@Attribute` might be a bit simpler. However, if you want to support dynamic changes to the `enabled` property, `@Input` is more appropriate.