Where the workflow shifted
When a page says an AI can call tools, readers need to know which actions run automatically and which stop for confirmation.
Separate reading, generating, submitting, paying, publishing, and deleting into confirmation tiers with logs, tests, and human takeover paths.
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
- Link today's tool-call card back to `ai-agent-governance`
- 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
Automation without visible confirmation reduces trial intent, even when the feature is powerful. Keep the original source open so the announcement, the evidence, and this site's interpretation stay separate.