GeezerVison

The built-in execute, process_output, and advisor tools offered an optional model_intent argument whose text replaced the tool row's default label. Models fill it inconsistently, so most chats mixed intent labels with plain command labels. On dogfood over three days, Claude Opus 5.5 sent it on 17% of execute calls through Bedrock and 30% through the Anthropic API. The rate follows reasoning effort: the few chats at max or xhigh effort sent it on every call, while chats at high, medium, or default effort sent it on about a third of calls or fewer.

This removes the argument from the three tool schemas and always renders the command-based labels ("Ran ...", "Started ... in the background", "Checked ...", "Consulted the advisor"). It also deletes the frontend helpers, tests, and stories that existed only for the intent labels.

• Old chats keep working. chatd's decoders and its tool input check ignore undeclared keys, so calls that still carry model_intent run as before and their rows show the default label.
• The per-server model_intent option for MCP tools is unchanged. That field is required in the schema, and Opus 5.5 fills it on 96 to 99.7% of those calls.
• The MCP workspace execute and process_output tools now match the Coder Agents contract apart from their workspace argument, so the golden test drops its Agents-only exception.
• Pixel diffs from this change: the deleted intent stories and the new default labels in AllToolIconsTranscript, PolicyBadgeCoversEveryRenderer, and StreamedAdvisorResultOverlaysDurableCall.

Testing

• go test for chattool, chatadvisor, toolschema, coderd/mcp, and coderd/x/chatd -run Advisor; go vet ./coderd/x/chatd/... ./coderd/mcp/....
• Red check: re-adding the field to ExecuteArgs fails TestWorkspaceToolsGolden.
• Vitest unit tests for the tool utils, the generic tool row, and chat parsing (5 files) and the affected Storybook files (4 files); biome, oxlint, and tsc.
• make pre-commit passed on the rebased head. The pre-push hook was skipped per the maintainer's standing preference; CI covers it.

Review record

• frontend-review (FE1 to FE10): all PASS or N/A.
• coder-frontend-review (8 parallel reviewer roles): no findings. Two optional side notes were declined: a nested ternary for ExecuteTool's label (SD3 discourages them) and a story for an old call that still carries model_intent (TS7: it shows the same state as the existing default-label stories).

Xum opened this PR on behalf of @ibetitsmike.