mlsanityData to 14 Oct 2026

Making OpenAPI Documentation Agent-Ready: Detecting Documentation and REST Smells with a Multi-Agent LLM System

arXiv 2605.14312 ↗First posted 14 May 2026cs.SEcited by 0

On the map: LLM agents and tool use → Software engineering coding agents

Abstract (arXiv)

The growing adoption of AI agents and the Model Context Protocol (MCP) has motivated organizations to expose existing REST APIs as agent-consumable tools. In our industrial context, this initiative targeted an ecosystem of 16 production APIs comprising approximately 600 endpoints. Although these APIs were stable and widely used within a microservice architecture, early proof-of-concept experiments revealed systematic failures in task planning, tool selection, and payload construction when accessed through MCP-based agents. Rather than attributing these failures to model limitations alone, we conducted an ecosystem-scale empirical assessment of the underlying OpenAPI documentation. We developed Hermes, a multi-agent LLM-based system that detects documentation and REST-related smells at the endpoint level and generates explainable diagnostic reports. The large-scale evaluation identified 2,450 smells across 600 endpoints, with deficiencies present in all analyzed operations. Practitioner validation confirmed high agreement with the detected issues while also revealing contextual trade-offs in remediation decisions. The findings suggested that structural validity within microservice environments does not guarantee semantic readiness for agent-based consumption. Based on this evidence, the organization revised its adoption strategy, prioritizing selective endpoint adaptation, redefining documentation standards, and integrating automated documentation assessment into API governance workflows. This case illustrates how systematic artifact-level evaluation can function as a strategic decision-support mechanism, reducing technological risk and guiding evidence-based AI adoption in industrial software ecosystems.

Key facts. No citing papers in the map yet (data through 14 Oct 2026). Placed in Software engineering coding agents, one of 16 directions in LLM agents and tool use. Builds on 4 of its 23 references that are in the map. First posted on arXiv 14 May 2026.

Builds on

4 of 23 references.

Closest ancestors · 1

Same direction, newest first

  1. 2025Doc2Agent: Scalable Generation of Tool-Using Agents from API Documentation24 Jun

Other references · 3

  1. 2025MCP-AgentBench: Evaluating Real-World Language Agent Performance with MCP-Mediated Toolscited by 32
  2. 2025We Urgently Need Privilege Management in MCP: A Measurement of API Usage in MCP Ecosystemscited by 15
  3. 2025A Framework for Testing and Adapting REST APIs as LLM Toolscited by 10

Built on by

Not cited yet.

Similar, not cited

Close in wording, no citation either way

  1. 2025From REST to MCP: An Empirical Study of API Wrapping and Automated Server Generation for LLM Agents
  2. 2026From Docs to Descriptions: Smell-Aware Evaluation of MCP Server Descriptions
  3. 2026Agent4Spec: An LLM-based Agentic System to Optimize API Specifications through Automated Validation and Market Analysis
  4. 2025From Specification to Service: Accelerating API-First Development Using Multi-Agent Systems
  5. 2026DADL: A Declarative Description Language for Enterprise Tool Libraries in LLM Agent Systems
  6. 2026Model Context Protocol (MCP) Tool Descriptions Are Smelly! Towards Improving AI Agent Efficiency with Augmented MCP Tool Descriptions
  7. 2026OOPS: Automated generation of REST API specification via LLMs ↗
  8. 2026AgentProv: Auditing Agentic LLM API Providers via Tool-use Policy Probes