You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Add description() metadata action and map it in the JSON Schema emitter
Downstream tool-parameter schemas need per-field descriptions to survive
AOT JSON Schema generation; until now the emitter dropped any metadata
with a "not representable" warning. description() is a pure pass-through
transformation (same runtime shape as readonly), so the compiled fast
path is unaffected, and the emitter folds it onto the accumulated schema
last-wins.
Closes#42
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01PXctopVx69rLttyhKbeoVE
Add a `description(text)` metadata action and map it to the JSON Schema `description` keyword
7
+
8
+
`description()` is a pure pass-through transformation (no runtime validation effect, same shape as `readonly`). The JSON Schema emitter now folds it onto the accumulated schema as the `description` keyword; piping it multiple times is last-wins. Per-property descriptions inside `object()` land on the property schema.
0 commit comments