PENGO Workbench
Workbench / Issues / Too Many Tool Calls

Issue

Too Many Tool Calls

The AI or agent makes more tool calls, searches, retrievals, API calls, or integration actions than the task requires or permits.

What This Looks Like

The AI or agent calls tools more often than the task needs. It may keep searching, retrieving, querying APIs, opening files, calling MCP tools, or repeating tool calls even after enough information is available. The user may see cost, latency, noise, or workflow complexity increase without a clear benefit.

Why It Matters

Tool calls are not just text. They can cost money, consume time, affect rate limits, expose data, modify state, or create review burden. Too many tool calls can turn a bounded request into an uncontrolled execution path, especially when an agent keeps looking for more evidence or more certainty.

Structural Signal

Tool use exceeds the declared or reasonable action boundary for the task. The issue is not that a tool was used; it is that tool execution is not bounded by a stopping rule, source limit, cost limit, or sufficiency condition.

Common Triggers

  • The task lacks a clear tool-use budget or stop condition
  • The agent treats uncertainty as permission to keep searching
  • Retrieval or search results create new branches instead of narrowing the task
  • The prompt rewards exhaustive checking without defining enough
  • Tool results are not summarized into a stable state before the next call
  • The workflow does not distinguish required tool calls from optional exploration

When to Use This Issue

Use this Issue when tool use itself becomes excessive, unbounded, repetitive, or disproportionate to the task.

When Not to Use This Issue

Do not use this Issue when multiple tool calls are required by the task and are bounded. Do not use it when the problem is one invalid tool call. This Issue applies when tool-call volume or repetition becomes the failure.

Category

MCP, Tools & Integrations

Primary Pattern

PAT-0400 — Unbounded Scope

Declared Patterns

PAT-0400

Unbounded Scope

A structural condition where an operation, authority, rule, or expansion has no declared upper bound, boundary, or termination condition.

PAT-0300

Escalation Growth

A structural condition where impact, authority, scope, or consequence increases across sequential states without a declared limiting mechanism.

PAT-0340

Overreach

A structural condition where actions, effects, authority, or modifications extend beyond declared scope without authorization.

Derived Primary Lenses

LEN-0120

Boundary Compliance Lens

Evaluates observed structure against declared boundary posture, including allow, block, and exception rules.

LEN-0160

Constraint Sufficiency Lens

Evaluates whether declared constraints are sufficient to eliminate structural degrees of freedom.

LEN-0190

Escalation Gradient Lens

Measures structural growth or intensification across sequential executions, states, or transitions.

LEN-0220

Isolation Boundary Lens

Evaluates whether structural constraints, effects, and regions remain contained within declared boundaries.

LEN-0240

Overreach Lens

Detects structure that exceeds declared scope or authority reach.

LEN-0290

Variance / Entropy Lens

Measures structural variability across repeated or comparable evaluations and identifies divergence beyond expected bounds.

Derived Secondary Lenses

LEN-0250

Propagation Lens

Traces how structural declarations, effects, or state changes propagate across boundaries or stages.

Related AI-Adjacent Issues

ADJ-0006

Agent Keeps Adding Tool Dependencies

An agent keeps adding required tools, connectors, searches, files, APIs, or integrations instead of completing the task with the available surface.

Search Intents

  • too many tool calls
  • AI called tools too many times
  • agent keeps calling tools
  • excessive MCP tool calls
  • AI overuses search tools
  • tool loop too many calls