container_start

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

No annotations are provided, and the description does not disclose behavioral traits such as whether the container must exist already, what happens if it's already running, or side effects. The output schema exists but the description does not hint at the return value.

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 brief but under-specified. It does not earn its place because it adds no useful information beyond the input schema's title. A concise description should be complete enough to guide usage.

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 that there is an output schema and sibling tools, the description is inadequate. It does not explain return values, preconditions (e.g., container must exist and be stopped), or postconditions. The tool is too important to have such a minimal description.

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?

With schema description coverage at 0%, the description should add meaning beyond the parameter name. It only repeats 'name to start the container' which adds no semantic value or constraints (e.g., format, allowed characters, examples).

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 'Starting a container' which is a clear verb+resource, but it does not distinguish from sibling tool 'run_container' which also starts a container (after creating it). The description could be more specific that this tool starts an existing container.

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?

No guidance is provided on when to use this tool versus alternatives like 'run_container' (which creates and starts) or 'container_restart'. The agent gets no context for decision-making.

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