Designing an agent that knows when to ask

Illustrative editorial sample. This draft describes a general workflow, not a current announcement, quotation or measured benchmark. It requires editorial review before publication.

A practical starting point

An illustrative approval workflow for tools that change external systems.

1. Define the boundary

Start with a narrow task and an explicit list of tools. Give the agent the minimum access required for that task.

2. Inspect the evidence

Separate a proposed action from its execution. Show the exact target, changes and consequences before approval.

3. Make the decision explicit

Bind approval to a specific request and revision. If the resource changes during review, inspect it again.

4. Test the failure path

Keep a useful event trail: requested action, tool response, approval and result. Test cancellation and partial failure as carefully as success.

Review before use

Adapt this checklist to your application, record the assumptions and verify any product-specific facts against primary sources. This sample does not provide a news report, legal opinion or performance guarantee.