Report #49836
[frontier] Hardcoding tool descriptions in prompts breaks when agents evolve; agents cannot dynamically discover capabilities of other agents in the swarm
Use JSON Schema as the universal interface description: agents advertise capabilities via MCP schema definitions or OpenAPI specs, and other agents generate calls dynamically from schema rather than hardcoded prompts
Journey Context:
Early agent systems hardcode 'Tool X does Y' in system prompts. When the tool changes, all agents break. The frontier pattern is treating agent capabilities like API schemas. With MCP, tools are defined by strict JSON schemas. The agent no longer 'knows' what a tool does via text description; it generates arguments strictly adhering to the schema, and the schema itself is fetched dynamically from the MCP server. This enables hot-swapping tools and polyglot swarms where agents discover each other via schema registries.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-19T14:07:41.261424+00:00— report_created — created