
A2A Explained: How Agent-to-Agent Communication Differs from MCP
MCP answers "what can I call?" A2A answers "who can I hand this to?" Different questions, different failure modes.
Read tutorialMethods for measuring AI-system behavior, validating claims, detecting regressions, and turning observed failures into actionable evidence.
Tagged articles
63 articles in this tag.

MCP answers "what can I call?" A2A answers "who can I hand this to?" Different questions, different failure modes.
Read tutorial
Your recall metric looks healthy. Your answers are still wrong. That gap is the whole reason advanced retrieval patterns exist.
Read tutorial
The demo worked because the agent was running on your laptop. It had your credentials, your network, your home directory, and your shell history. Move it…
Read tutorial
A prompt fix that passes the demo and fails two weeks later is not a bad prompt. It is an improvement process with no memory.
Read tutorial
An agent that has run forty steps and produced an answer no better than step three is not stuck. It is broken in a specific, nameable way.
Read tutorial
A user reports a wrong answer. You pull the trace. Every tool call succeeded, every span is green, latency is normal, and no error was logged anywhere. The…
Read tutorial
Every agent builder hits the same wall. The first working agent is small: a system prompt, a few tools, a loop. Then someone needs release notes. Someone…
Read tutorial
The demo works. The agent books the flight, summarizes the repo, files the ticket. Then you point it at a task with one extra branch, and it calls the same…
Read tutorial
A user types three words into your assistant. The model returns a confident, well-formatted, entirely wrong answer to a question nobody asked. The user…
Read tutorial
Hop three. The context window is full. Half of it is plausible garbage — passages that matched the query, ranked well, and turned out to be useless. The…
Read tutorial
A retrieval system can only return what a chunk contains. Cut the answer in half, and no reranker will put it back together.
Read tutorial
A scanner that flags ten thousand findings and a researcher who proves three are both "finding vulnerabilities." Only one of them has evidence you can…
Read tutorial
The agent writes the function, re-reads it, decides it looks correct, and stops. The code is wrong. This is the most common failure in autonomous coding,…
Read tutorial
A RAG feature ships. The answers read well. Someone wires up a faithfulness evaluator, the number lands at 0.87, and within a week that single scalar is…
Read tutorial
The request fits. It returns a worse answer than the shorter prompt you shipped last week.
Read tutorial
A vector search returns its nearest neighbors whether or not those neighbors answer the question. The pipeline reports no error, the generator receives…
Read tutorial
The first sub-answer is wrong, and every later step inherits it with full confidence.
Read tutorial
You have seen the failure. A research agent returns a polished report, the citations look real, and the first URL you check resolves to a page that does…
Read tutorial
The demo works. The agent reads the queue, drafts the update, and posts it. Then someone asks who approved the change, which run produced it, and how to…
Read tutorial
The demo works on turn one. By turn five, the agent is answering a question you already answered, citing a document it retrieved three turns ago, and…
Read tutorial
A retrieval system fails in a specific, repeatable way. You ship a demo that answers paraphrased questions beautifully, then a user pastes an error code, a…
Read tutorial
An evaluator is only as useful as the set of distinct repair actions its output can select.
Read tutorial
Your few-shot set passes every happy-path test, then folds the moment a real input arrives with an extra clause, an unusual label, or a phrasing you did…
Read tutorial
"Self-improving agent" is three different mechanisms wearing one coat. Pull the coat off and you find a memory that accumulates, a skill file that gets…
Read tutorial
The demo worked. Then the corpus grew, the questions started requiring synthesis across documents, and the same pipeline that felt magical last month now…
Read tutorial
You have a routing step in an agent pipeline. Four possible destinations. The LLM call costs a full generation, 1–2 seconds, and a token bill. The answer…
Read tutorial
Ask a system to synthesize five documents into one answer. It does the work. Ask the same question tomorrow, and it does the work again, from scratch, with…
Read tutorial
The agent ran clean for forty steps. Then it re-ran a migration it had already finished, forgot the constraint the user stated at turn three, and quietly…
Read tutorial
An agent processes 200 units of work over four hours, dies on unit 201, and restarts from zero. The crash is not the failure. The failure is that nothing…
Read tutorial
The agent remembered everything and still got the user wrong. It recalled a preference the user had abandoned six months ago, re-derived a workflow it had…
Read tutorial
A goal-based agent that never terminates is not a model failure. It is a contract failure.
Read tutorial
Your agent has thirty tools, four MCP servers, and a plan-mode toggle. It still fumbles a routine refactor, and when it does, you cannot tell whether the…
Read tutorial
An agent that plans beautifully and then executes a stale plan into a wall is not a planning failure. It is a state failure.
Read tutorial
A plan that reads like a clean numbered list can still deadlock at runtime, because the list never told the scheduler which steps actually depend on which…
Read tutorial
The demo works. You paste a gnarly task into one prompt—extract the entities, reconcile them against the schema, flag the contradictions, write the…
Read tutorial
A prompt that passed review, shipped, and then quietly broke a downstream consumer is not a prompt problem. It is a specification problem wearing a prompt…
Read tutorial
The prompt worked on your laptop. In production, the same prompt returns a paragraph on Monday, a bulleted list on Tuesday, and a confident fabrication on…
Read tutorial
A single greedy decode is right most of the time and wrong with total confidence the rest. The instinct is to sample more and let the answers vote. But…
Read tutorial
A prompt is not a sentence you tune. It is a versioned artifact whose behavior is a distribution, and you cannot manage a distribution by reading three…
Read tutorial
A thread pool that scales on network calls and flatlines on arithmetic is not a mystery. It is the Global Interpreter Lock doing exactly what it was…
Read tutorial
Watch a real session. A user types: "Compare the latency and cost of the two reranking options we discussed, for our EU deployment." Your hybrid retriever…
Read tutorial
An agent that acts without reasoning is not reasoning. It is guessing with a tool schema.
Read tutorial
The model gets the answer wrong, and it is not because it did not know something. It dropped a constraint. It merged two cases that should have stayed…
Read tutorial
A coding agent is handed a fixed training script and a fixed success metric: make it run faster without breaking correctness. It rewrites, runs, times, and…
Read tutorial
You add a critique-and-revise step. The output gets longer, more confident, more padded with caveats. Your eval score does not move.
Read tutorial
A team adds a "reflect" step to their agent. Scores tick up a few points. Encouraged, they bolt on a memory buffer so the agent can "remember its…
Read tutorial
That failure breaks the "bad answer means bad instruction" reflex. Sometimes the instruction is fine, and the bottleneck sits somewhere else: the model…
Read tutorial
The retriever found the right document. The answer is still wrong. Somewhere between the vector store and the prompt, the evidence got buried under five…
Read tutorial
A prompt that grew from three lines to thirty is not a better prompt. It is a prompt nobody has tested.
Read tutorial
That is the shape of the failure I keep seeing in agent systems that look governed and are not. A team writes a planner prompt, a coder prompt, a reviewer…
Read tutorial
A linear agent loop is a commitment device. It commits to one trajectory, and every later step inherits the consequences of the earliest mistake.
Read tutorial
You ask the model to critique its own draft. It returns: "The response is clear and well-structured, but could be more specific." You ask it to revise. The…
Read tutorial
The loop that improves the harness can also edit the evaluator, the permissions, and the rollback path. That is the whole problem in one sentence.
Read tutorial
Always-on retrieval is a fixed policy applied to a variable question distribution. It over-retrieves on questions the model already knew, and it…
Read tutorial
Two teams run the same model on the same task. One ships reliably. The other drowns in tool-call latency, context bloat, and incidents nobody can explain…
Read tutorial
A failed agent run rarely looks like an interface problem. It looks like a model problem: wrong tool, malformed arguments, an error swallowed and retried…
Read tutorial
The release gate is green. Schema validation passed, the golden set passed, the benchmark score ticked up, and the guardrails logged zero trips. Two days…
Read tutorial
Two teams ship the same model, the same prompt, the same tool list. One agent finishes a multi-step task. The other stalls, loops, and quietly corrupts its…
Read tutorial
Two seed-stage teams ship an LLM-backed product. Same headcount, same model access, same demo polish. Eighteen months later, one compounds while the other…
Read tutorial
The prompt you spent a week tuning is not what the model reads. It reads everything in the window — and everything else is quietly voting.
Read tutorial
The demo works. Then you add a second worker, a shared artifact store, and a verifier, and the system starts producing results nobody can attribute,…
Read tutorial
A prompt is a spark, not an engine. The spark still matters — it just cannot carry the machine.
Read tutorial
The demo works. The real inputs don't. Same prompt, same model, and suddenly the output is the wrong shape, the wrong label, or confidently on the wrong…
Read tutorial