Docker start

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

Annotations already indicate destructiveHint=true and readOnlyHint=false, so the agent knows this is a mutating operation. The description adds no additional behavioral information such as side effects, state changes, or required container existence. It does not contradict annotations, but fails to enrich them.

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 extremely concise with a single sentence, but it is under-specified rather than efficiently front-loaded. There is no wasted wording, but the lack of essential details means it does not earn its place as a standalone definition.

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?

Given the tool is simple with one parameter, the description should cover at least the container identifier and expected behavior. It does not mention what happens if the container is already running, whether it must exist, or the output format. The output schema exists but is not shown, so the description carries responsibility for usage context, which it fails to provide.

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 'container' with no description, and schema coverage is 0%. The description does not explain what the container parameter should be (ID, name, format) or any constraints. This is a critical gap because the agent has no guidance on how to fill the parameter correctly.

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 'Start a container' clearly states the verb and resource, making the primary action unambiguous. However, it does not differentiate from sibling tools like docker_stop, docker_restart, or docker_exec, though the distinct verb helps. It is specific enough for an agent to know what it does, but lacks context about scope.

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?

There is no guidance on when to use this tool versus alternatives such as docker_restart or docker_start with specific flags. No exclusions, prerequisites, or conditions are mentioned. The description merely states the action without any usage context.

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