The short version
Claude follows the action implied by your wording. “Suggest improvements” asks for advice. “Implement the improvements in this document” asks for a change. Clear verbs reduce the gap between the outcome you expect and the task Claude believes it has been given.
Three parts of an action request
Use a simple contract:
- Action: edit, create, update, research, send, or advise.
- Capability: the file, tool, application, or system involved.
- Completion: the observable state that proves the work is finished.
Constraints belong beside that contract. State what must be preserved, what may not be inferred, and when Claude should stop for approval.
Example
A request to “suggest ways to improve this report” correctly invites a list. If the intended outcome is a revised document, ask Claude to review and edit the existing report, preserve its section structure and factual figures, and finish with a short change summary.
The same distinction matters in tool-enabled workflows. “What should I send?” is analysis. “Draft the message and send it using the available email tool” requests an external action and should also state any approval boundary.
Avoid accidental autonomy
Clarity works in both directions. When you want recommendations only, say that Claude must not modify files or take external action. Explicit restraint is as useful as explicit execution.
Practical checklist
- Choose a verb that matches advice or action.
- Name the object or system to be changed.
- State important preservation rules.
- Define the finished state.
- Add an approval point for consequential external actions.
- Ask for a concise outcome summary when traceability matters.
Try it
Take one prompt that begins with “Can you suggest.” Decide whether you really want advice or implementation. Rewrite it with a specific action, capability, constraints, and completion condition.