fix: name run_code's required description argument in its model-facing prose
The transport schema requires both `code` and `description`, but the tool
description and both SDK instruction flavors described the call as passing a
program. `description` was reachable only through the parameter schema, so a
model following the prose emitted `{code}` alone and lost the whole written
program to an INVALID_ARGS rejection.
The length and format guidance stays in RUN_CODE_DESCRIPTION_PARAM_DESCRIPTION
alone, so the schema and the prompt cannot drift.
Fixes #2426
This commit is contained in:
@@ -2,5 +2,5 @@
|
||||
# side as of the last confirmed-consistent state. Both languages carry equal authority;
|
||||
# after editing either side, bring the other along and re-record with:
|
||||
# pnpm run verify-translation-pairing --write docs/tool-catalog.md
|
||||
tool-catalog.md: 898c5700eddfe49083b2ce0e3e04761298b28bbb
|
||||
tool-catalog.zh.md: 3b17cf4e3b1b74b0735783cfe899c9c693146c38
|
||||
tool-catalog.md: b90a17c7a028b8212fbbcabe2490029de0e44d77
|
||||
tool-catalog.zh.md: fff2af027415ca0031926bdf79ce41f006d80a50
|
||||
|
||||
Reference in New Issue
Block a user