Overview

Add a top-level CLI command, docker agent toolsets, that lists every built-in toolset type available for use in an agent configuration (the values you can put under toolsets: - type: <name>), each with a one-line summary and a link to its docs. Support --format table (default) and --format json.

Motivation

When writing an agent YAML you reference toolsets by type:

toolsets:
  - type: filesystem
  - type: shell

…but there is currently no way from the CLI to discover which types exist or what they do. The authoritative list lives only in Go source (DefaultToolsetCreators() in pkg/teamloader/toolsets) and the JSON schema. New users have to read the docs site or source to find out that rag, mcp_catalog, lsp, background_jobs, etc. exist.

The CLI already has docker agent models to discover available models - there is no equivalent for toolsets. This closes that discoverability gap and keeps the two feeling symmetrical.

Use cases

1. A user scaffolding a new agent runs docker agent toolsets to see what built-in tools they can add, and reads the summary to pick the right ones.
2. Automation/scripting: docker agent toolsets --format json | jq -r '.[].type' to enumerate types (e.g. to validate a config generator).
3. Quickly jumping to a tool's documentation via the docs URL in the JSON output.

Proposed solution

• New top-level command docker agent toolsets in the Diagnose command group (mirrors docker agent models).
• --format table|json flag (default table).
• Backed by a small catalog (type, summary, docs) that is the single source of truth, kept in lockstep with the toolset creator registry by a unit test so the two can never drift.

Example:

$ docker agent toolsets
TYPE                SUMMARY
filesystem          Read, write, list, search, and navigate files and directories
shell               Execute shell commands in the user's environment
think               Step-by-step reasoning scratchpad for planning
...

Alternatives

• docker agent debug toolsets <agent-file> already exists, but it is hidden, requires an agent file, and lists a specific agent's instantiated tools - not the catalog of available types. It does not answer "what types can I use?".
• Today the only workarounds are reading the docs site, the JSON schema, or pkg/teamloader/toolsets source directly.

Related issues

None found - searched issues, CLI, docs, git history, and CHANGELOG.md; no existing command lists built-in toolset types.

Additional context

No response