A tool interface names an operation, validates inputs, reports outputs and failures, and constrains side effects. Natural-language descriptions alone are not an execution contract.

Tool Interfaces Are Typed Boundaries

In this situation—allowing an agent to create a calendar event only with valid fields—which choice best applies “Tool Interfaces Are Typed Boundaries”?

A router selects a specialist, tool, or path from evidence about the request and declared capability. It needs a fallback when no option is suitable or confidence is low.

Routers Match Requests to Capabilities

A state schema names fields, types, ownership, and update rules shared across a graph. It makes incompatible updates visible and supports safe persistence and replay.

State Schemas Preserve Meaning Across Nodes

A tool schema defines required fields, types, allowed values, and returned forms. Validation before execution prevents malformed model output from becoming an external side effect.

Learn Before

Related