container_start

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

Description adds behavior beyond annotations: idempotent on running containers returns 304, and returns full inspect payload. Annotations already indicate read/write and non-destructive, so description provides useful extra context.

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?

Concise: single paragraph with clear purpose, usage, and parameter/return summary. No wasted words, well-structured.

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?

Covers all aspects for a simple tool: when to use, behavior on running, parameter format, return value. Slightly missing mention of prerequisite that container must exist, but implied by 'existing stopped container'.

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?

Parameter id_or_name is explained as 'Container id (full or short) or name', adding meaning beyond the schema type. With 0% schema coverage, this compensates well.

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 'Start an existing stopped container' with a specific verb and resource. It clearly distinguishes from sibling tools like container_run and container_restart.

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?

Explicit guidance: use for stopped containers, not for running ones (no effect), alternatives provided for creating+starting (container_run) and stop+start (container_restart).

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