collect_managed_docker_workload

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

The description adds useful behavior beyond the destructiveHint annotation: it creates a temporary container, waits for Broker readiness, and explicitly cleans only the verified container, scoping the destruction conservatively. It also implies blocking behavior with 'wait.' No contradiction with annotations exists.

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 a single dense sentence with no filler; every clause adds a behavioral or scoping constraint. However, the run-on structure and heavy jargon make it less immediately scannable than ideal.

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 lifecycle is described and an output schema exists, but for a 9-parameter destructive tool with no parameter descriptions and no usage guidance, the description is not sufficient for an agent to confidently select the right configuration. It lacks session prerequisites, parameter semantics, and clear routing among many sibling collection tools.

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 0% description coverage across 9 parameters, and the description does not mention any parameter name or concept such as mode, events, call graph, frequency, duration, output limits, or timeout. It also does not clarify what session_id refers to, leaving parameter meaning almost entirely to inference from names, enums, and defaults.

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 lifecycle: it creates one temporary container from an already-local immutable image, holds the workload at the package Gate, runs/collects, waits, and conservatively cleans only that verified container. This gives a clear verb/resource pair and includes enough detail to distinguish this managed collection workflow from sibling collection tools.

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 implies a precondition with 'already-local immutable image' and 'until Broker collection is ready,' but it never explicitly tells an agent when to choose this tool over alternatives such as collect_docker_optimization_workload or collect_docker_target. No exclusions or comparison guidance is provided.

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