A tool that declares no input arguments still renders an Arguments heading followed by "This tool does not define input arguments." e.g.
ToolArgumentsForm.tsx:211-222 always renders the section and its heading, and adds the empty message when spec.fields.length === 0. The complex schema case returns earlier at line 168, so an empty field list at that point means the tool has no arguments rather than arguments the form could not render.
Proposed change: render nothing when the field list is empty, and remove the tools.details.preview.arguments.empty string along with its translations.
The generated snippet continues to show empty arguments for such a tool, which is accurate and should stay.
This is the same component as items 3 and 4 of #6860 and can be picked up alongside them.
Scope is the web UI only, no API change, and no work on the Admin UI. This surface is live in the Tools drawer today.
Reactions are currently unavailable
A tool that declares no input arguments still renders an Arguments heading followed by "This tool does not define input arguments." e.g.
ToolArgumentsForm.tsx:211-222 always renders the section and its heading, and adds the empty message when spec.fields.length === 0. The complex schema case returns earlier at line 168, so an empty field list at that point means the tool has no arguments rather than arguments the form could not render.
Proposed change: render nothing when the field list is empty, and remove the tools.details.preview.arguments.empty string along with its translations.
The generated snippet continues to show empty arguments for such a tool, which is accurate and should stay.
This is the same component as items 3 and 4 of #6860 and can be picked up alongside them.
Scope is the web UI only, no API change, and no work on the Admin UI. This surface is live in the Tools drawer today.