Option A describes an under-specified prompt. Naming only a topic does not tell Claude what action to perform, who will use the result, which information should receive priority, or how the response must be organized. Claude must then infer these requirements, increasing the likelihood of a generic, mis-scoped, or incorrectly formatted response.
An effective business prompt normally identifies the task, supplies relevant context, defines the intended audience, states the desired output structure, and includes material constraints such as tone, length, scope, or exclusions. A representative example can further clarify the expected standard. Consequently, Options B, C, and D describe techniques that generally reduce ambiguity rather than cause it.
Anthropic’s prompting guidance recommends clear, detailed instructions and relevant context, while its prompt-engineering framework assumes that users first define success criteria and a testable objective. The prompt should make the expected behavior observable: “summarize this policy for store managers in a five-bullet briefing” is materially stronger than “employee policy.” When an output is vague, the correct diagnosis is usually not insufficient model capability but insufficiently described intent, audience, or format. Claude usage and prompting guidance
================
