preview_docker_optimization_session

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide idempotentHint and destructiveHint, and the description adds useful behavioral context: no build/pull side effects and a mandatory user confirmation gate before authorization. This goes beyond the structured annotations and helps an agent understand the tool's non-obvious workflow role.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is short and front-loads the main action and constraints. However, phrases like 'exact authorized build context' and 'content-bound one-confirmation optimization summary' are needlessly opaque and could be clearer without adding length.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

The output schema likely covers return value structure, so that is not a gap. But the required allowed_modes parameter is completely unexplained, and the description only weakly situates this tool in the broader workflow. The 'must confirm before authorization' line helps, but it is not enough for confident invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

The input schema has one required parameter, allowed_modes, with 0% schema description coverage, yet the description never mentions it or explains how to choose among stat, record, sched, off_cpu, and lock. The agent is left to infer the meaning of 'authorized build context' and cannot reliably populate the required parameter.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Does the description clearly state what the tool does and how it differs from similar tools?

The description states a concrete action ('Capture... and return... summary') and a clear resource (docker optimization session), with explicit non-goals ('does not build or pull'). The meaning is somewhat obscured by jargon like 'content-bound one-confirmation optimization summary,' but it is generally distinguishable from build/authorize siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description clearly indicates this is a preview step: 'The user must confirm this exact Preview before authorization.' It also excludes build/pull use cases, which helps an agent choose it over build_docker_optimization_candidate or authorize_docker_optimization_session, though it never names those alternatives explicitly.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.