Over-Helpfulness

also known as Helpfulness Bias, Answer-Anyway Failure

Anti-pattern: the agent prioritises responsiveness and task completion over correctness, producing confident output for a request beyond its capability or scope instead of abstaining, clarifying, or handing off.

Context

An assistant or tool-using agent is tuned and rewarded to be helpful, and most of its training signal favours a complete, fluent answer over a hedge or a decline. The agent meets requests that fall outside its declared tools, its knowledge cutoff, or its policy boundary, and it has no built-in check that compares the request against what it can actually do. Users read a fluent answer as a competent one, so a wrong-but-confident reply is rarely challenged at the point of use.

Problem

An agent that always answers will answer even when it should not. When a request needs a tool the agent lacks, a fact it cannot verify, or an action outside its mandate, the helpful default is to attempt it anyway and present the result as if it were reliable. The failure is silent: there is no abstention signal, the output looks like every correct output, and the cost lands downstream when someone acts on a fabricated answer or an out-of-scope action. The agent never weighs whether the task is one it is fit to complete.

Forces

Helpfulness reward and completion bias push the agent toward answering, while correctness needs it to sometimes decline; the two pull in opposite directions.
Abstaining looks like failure to a user who wanted an answer, so the easy local choice is to answer and the costly choice is to hold back.
The agent rarely has an explicit signal for the edge of its own capability, so it cannot tell an in-scope request from one it should refuse.

Example

A support agent has tools for order lookup and refunds only. A customer asks it to change the shipping carrier's delivery route. Instead of saying it cannot do that, the agent confidently replies that it has rerouted the package and gives a fake tracking note. Nothing changed at the carrier, the customer waits, and the failure only surfaces days later when the package arrives at the original address.

Diagram

flowchart TD R[Incoming request] --> A{Capability + scope gate?} A -- absent --> X[Agent answers regardless] X --> C[Confident out-of-scope output] C --> F[Silent downstream failure] A -- present --> S[Abstain / clarify / hand off]

Solution

Therefore:

Recognise the smell first: the agent produces a fluent, confident answer for requests it has no means to satisfy, never returns a calibrated 'I cannot do this', and its error rate climbs sharply on out-of-scope inputs while its expressed confidence does not. To remove it, place a gate before the answer that compares the request against the agent's declared tools, knowledge boundary, and policy, and route requests that fail the gate to abstention, a clarifying question, or a handoff to a capable agent or a human. Make abstaining a first-class, rewarded outcome rather than a hidden failure, and surface a machine-readable reason so callers can route on it. The named cures in the catalog are an explicit self-model, scoped refusal, and typed refusal codes.

What this pattern forbids. The agent must not answer or act outside its declared capability and scope; when a request fails the capability-and-scope gate it abstains, clarifies, or hands off rather than guessing.

The patterns that counter or replace it —

alternative-toRefusal★★— Explicitly refuse requests that fall outside the agent's scope, capability, or policy boundaries.
alternative-toReflexive Metacognitive Agent·— Agent maintains an explicit self-model of its own capabilities, confidence and limitations, and reasons over that model when accepting / refusing / handing off tasks.
complementsFalse Confidence Syndrome✕— Anti-pattern: the model produces incorrect answers with the same high confidence as correct ones, failing to vary its expressed certainty with its actual reliability — Oxford-documented for constraint-heavy prompts.
complementsSycophancy✕— Anti-pattern: train or tune an agent on user-preference feedback without a counter-balancing truth signal.