get-creative-features: endpoint name is ambiguous - consider rename to evaluate-creative or assess-creative

[bokelley]

Problem

The get_creative_features endpoint evaluates a creative manifest against a governance agent and returns feature values for that creative:

"Evaluates a creative manifest and returns feature values from a creative governance agent."

The name get_creative_features is ambiguous — it could mean:

1. Get the list of available features (feature discovery)
2. Evaluate a creative and return its feature values (feature evaluation)

The current endpoint does #2, but the name suggests #1. This creates a discoverability problem: agents reading the capability manifest may not understand that get_creative_features is an evaluation endpoint requiring a creative_manifest input, not a catalog endpoint.

Impact

• Agents may not find the evaluation endpoint when looking for "assess creative" or "evaluate creative"
• The name could conflict with a future "list supported features" discovery endpoint
• The spec description itself says "task" ("Request payload for get_creative_features task") which conflicts with the synchronous nature of the endpoint

Proposed Fix

Consider renaming to one of:

• evaluate_creative — most direct
• assess_creative — common in brand safety/governance context
• get_creative_assessment — noun-form consistent with get_signals, get_products

If renaming is not feasible, at minimum clarify the spec description to say "evaluation" rather than "task", and add a note distinguishing this from any future feature-discovery endpoint.

Affected Schemas

• creative/get-creative-features-request.json
• creative/get-creative-features-response.json
• creative/creative-feature-result.json

[bokelley]

Resolved in #1252.