start_container

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

The description includes a '[WRITE][risk=medium]' tag and states the action is to start a stopped container. While it discloses the write nature and risk level, it lacks details on side effects, failure modes, or dependencies. Since no annotations are provided, the description carries the full burden and could be more thorough.

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 succinct, using a docstring format with clear sections. It front-loads the main action and risk level, then quickly covers parameters in a list. Every sentence serves a purpose, with no extraneous text.

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 tool has three parameters and no output schema, and the description covers the action and all parameters adequately. It could mention prerequisites (e.g., container must be stopped) or what happens if already running, but overall it provides enough context for correct usage.

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?

Despite the schema having 0% description coverage, the description provides clear meanings for all three parameters: container_id as 'Container id or name', dry_run as 'If True, preview without starting', and target as 'Target name from config; omit for the default'. This adds significant value beyond the schema's type information.

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 clearly states 'Start a stopped container' providing a specific verb and resource. It distinguishes itself from sibling tools like stop_container by noting it is the inverse. The purpose is unambiguous.

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 gives guidance on using dry_run for preview and explains the target parameter as omitting for default. However, it does not explicitly contrast with other container tools like restart_container or update_container, leaving some ambiguity about when to use this over alternatives.

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