A prototype can let an assistant call an external function directly; production action requires stronger control. Booking appointments, submitting insurance checks, and similar operations create consequences that multiply with scale, so tool access needs governed discovery, credentials, execution, and rate limits. section 6.0
A managed tool is a platform-governed capability rather than an application-local function. The platform assigns identity, tracks lifecycle and ownership, controls permissions, manages credentials, and executes the integration; applications declare the capabilities they need. section 6.1
A managed tool typically records:
- A unique name, description, version history, owner, and access policy. section 6.1
- Operational limits such as requests per session, with execution controlled centrally. section 6.0
Register once, discover wherever authorized
A scheduling integration can be registered as healthcare.scheduling.book_appointment with patient and slot parameters, a clinic API endpoint, non-read-only and non-idempotent behavior, and a three-request session limit. An authorized application can then discover tools in the healthcare.scheduling namespace and pass the returned definitions directly to model function calling.
