ToolInput

The input of one tool call.

Every agent tool defines its own input schema, so a call arrives as data of any shape. Writing that shape out as a line loses the one thing that makes a long call readable — which value belongs to which name — so it is kept, and the host styles it.

Three shapes cover what tool schemas use: one value, several values, and named parts. A number, a flag or an absent value is already a Value by the time it arrives: how a vendor writes its data as text is a question for the adapter that knows that vendor, never for a producer or a host.

Order is the contract's own. Named parts keep the order they were given, so the same call always reads the same way.