start_container

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

Discloses idempotent behavior on already-running containers (returns 304, no error), which goes beyond the readOnlyHint and destructiveHint annotations. Also describes args and returns.

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?

Perfectly concise: two short paragraphs plus args/returns. Every sentence adds value. Information is front-loaded with purpose and usage first.

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?

All necessary context is provided: purpose, usage guidance, behavioral traits, parameter meaning, and return type. No gaps remain for a simple start tool.

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 0% schema coverage, the description fully explains the parameter 'id_or_name' with its type (id or name) and that it is required. The arg description compensates entirely for the missing schema documentation.

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?

Clearly states 'Start an existing stopped container' with a specific verb and resource. Differentiates from siblings like run_container and restart_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?

Explicitly provides when to use (stopped containers) and when not (use run_container for new containers, restart_container for stop-then-start). Includes alternative tool names.

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