Where the workflow shifted
Anthropic agents and tools documentation places tools, context, and execution inside agent design, which helps split client projects into read, draft, submit, modify, and high-risk confirmation levels.
Service pages should say which actions are read-only, which draft work, which submit changes, and which require confirmation around money, customer data, or production systems.
Tool names are not outcomes
The signal matters when it changes how a team ships, reviews, or recovers work, not when it only names another tool.
Check permissions and failure
- Rewrite the delivery table around five permission levels and the client authorization each level needs
- Keep the test narrow: one low-risk task or tool entry before connecting permissions, logs, failure handling, and human takeover to production
What still needs proof
Complex automation fails on security and responsibility boundaries when permissions are not explicit. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.