Multi-Agent Systems Intro Flashcards

(41 cards)

1
Q

Why do agents often perform better when they’re specialized?

A

Because narrower tools + narrower instructions make behavior more consistent, predictable, and easier to get right.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What problem motivates multi-agent systems?

A

Some tasks require broad capabilities that don’t fit cleanly into one focused agent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

What is a “multi-agent system” in this lesson?

A

A setup where multiple specialized agents collaborate, usually coordinated by a manager/coordinator.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

What is the role of the coordinator agent?

A

Maintain the overall thread of execution and delegate sub-tasks to specialized agents.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

What is a useful analogy for the coordinator agent?

A

A project manager that assigns work and assembles results.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

How does delegation work in a multi-agent workflow?

A

The coordinator hands a sub-task to a specialist agent, waits, then uses the returned result to continue.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

In the meeting example, what might the scheduler agent return?

A

The meeting time and possibly the list of available participants.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

In the meeting example, what might an agenda agent return?

A

A meeting agenda tailored to the meeting’s purpose.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Why might scheduling logic differ from agenda-writing logic?

A

Scheduling needs constraints and availability reasoning; agenda-writing may be creative and structure-driven.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What is the risk of putting all rules into one giant system prompt?

A

Rules for one subtask can “pollute” another and make the agent confused or inconsistent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What does “pollution” mean here?

A

Instructions that make sense in one context interfere with decisions in another context.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

How do multi-agent systems reduce instruction pollution?

A

By isolating system instructions per specialist agent.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the benefit of “clean, isolated system instructions”?

A

Each agent stays focused and less distracted, improving reliability.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

How do tools relate to multi-agent specialization?

A

Each specialist agent can have only the tools it needs, reducing misuse and confusion.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is the typical tool-count advantage of multi-agent design?

A

You can replace one agent with many tools with several agents, each with 1–2 tools.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

Why can fewer tools per agent improve performance?

A

The agent’s allowed action space is smaller and easier to reason about.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

How is this similar to “tool specificity” principles?

A

Narrower, clearer options make it easier for an agent to choose the right action.

18
Q

What is a common failure mode of “one giant agent with all tools”?

A

It becomes unpredictable and harder to control because it can do too many things.

19
Q

What is the maintenance advantage of multi-agent systems?

A

You can change one agent without destabilizing the whole system.

20
Q

Why is it easier to reason about changes in a multi-agent system?

A

Each agent is a smaller module with fewer tools and simpler instructions.

21
Q

How does multi-agent design support testability?

A

You can test each specialist agent in isolation with targeted test cases.

22
Q

Why is testing a “big morass” agent harder?

A

A change can have unexpected ripple effects across many tools and instructions.

23
Q

What does “modular” mean in the context of agents?

A

The system is divided into smaller parts (agents) with clear responsibilities and interfaces.

24
Q

What is the core tradeoff introduced by multi-agent systems?

A

You gain modularity and focus, but you must manage communication and coordination.

25
What new design concern appears in multi-agent systems?
Communication: how agents pass tasks, context, and results to each other.
26
Why is “communication” important between agents?
The coordinator must understand results and decide what to do next.
27
What should a specialist agent ideally return to the coordinator?
A clear, structured result that is easy to use downstream.
28
Why is “waiting for the specialist agent” mentioned?
Coordination often involves sequential steps where one result is needed before continuing.
29
What is a key reason to avoid “one agent with multiple personas mixed together”?
Mixed rules and styles can conflict and reduce predictability.
30
How does multi-agent design improve predictability?
Each agent’s behavior is narrower, so outputs vary less and are easier to anticipate.
31
What is the “broad reasoning” challenge this lesson addresses?
Complex tasks need multiple distinct reasoning modes that don’t belong in one prompt.
32
What is the simplest multi-agent pattern described?
One coordinator delegates to specialist agents at different points in a workflow.
33
In this pattern, who “owns” the overall goal?
The coordinator agent.
34
In this pattern, who “owns” subtask expertise?
The specialist agents (scheduler, agenda builder, etc.).
35
What happens if you need a new capability in a multi-agent system?
Add or upgrade a specialist agent rather than bloating the coordinator prompt.
36
What happens if you need to change meeting scheduling rules?
Update the scheduler agent’s instructions/tools without touching other agents.
37
What is the benefit of “narrow and clean rules” per agent?
Less confusion, fewer edge-case interactions, easier debugging.
38
How is multi-agent design like good software architecture?
It’s modular: smaller components with clear interfaces are easier to maintain and test.
39
What is the key reason multi-agent systems can be “cheaper”?
Smaller prompts and fewer tools per agent can allow smaller models for subtasks.
40
What is the key reason multi-agent systems can be “safer”?
Specialists can be constrained with limited tools and strict guardrails for their domain.
41
What is the next topic this lesson leads into?
How agents communicate and coordinate (handoffs, message formats, shared context).