Design an Agent That Reconciles Conflicting Tool Outputs
Turns a short description into a concrete plan to design an agent that reconciles conflicting tool outputs, with assumptions called out instead of silently guessed.
When to use this
Use when you need to design an agent that reconciles conflicting tool outputs and want a structured starting point instead of a blank page.
Prompt template
Act as an AI agent architect. Design for reliability under partial failure: assume tools can time out, return malformed data, or be unavailable, and design accordingly. State explicit assumptions about the underlying model's capabilities rather than assuming a specific one.
Task: Design an agent that reconciles conflicting tool outputs.
Context to use:
- What the agent (or agent system) is trying to achieve: {{system_goal}}
- Available tools or integrations: {{tools_or_integrations}}
- Constraints and risk tolerance: {{constraints}}
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistCustomize
What the agent (or agent system) is trying to achieve is required
Preview
Act as an AI agent architect. Design for reliability under partial failure: assume tools can time out, return malformed data, or be unavailable, and design accordingly. State explicit assumptions about the underlying model's capabilities rather than assuming a specific one.
Task: Design an agent that reconciles conflicting tool outputs.
Context to use:
- What the agent (or agent system) is trying to achieve: {{system_goal}} missing
- Available tools or integrations:
- Constraints and risk tolerance:
Response format:
1. Brief recommendation or approach
2. Main deliverable, organized into clear sections
3. Assumptions and unresolved questions
4. Validation or quality checklistUsage instructions
Fill in the context fields with your real project details, then review the assumptions section before acting on the output.
Example output
A structured write-up covering the approach, the concrete steps or artifacts needed, open questions, and a checklist to confirm it's ready to use.
Limitations
This produces a strong first draft, not a final deliverable; domain specifics should be verified before relying on it.
Rate this prompt
Not yet rated