podman_container_start

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

Annotations already indicate the tool is idempotent and non-destructive, but the description adds no context about behavioral side effects, such as what happens if the container is already running, failure modes, or resource implications. It offers zero additional behavioral transparency.

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 short but under-specified; it merely restates the tool name and does not earn its place by adding useful information. It is concise in length but lacks necessary structure or elaboration.

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?

For a simple tool this description is bare minimum, but it lacks important context such as preconditions, state changes, or relationship to sibling tools. The presence of an output schema reduces the need to explain return values, yet the description still feels incomplete for an agent to select and invoke correctly.

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 schema has a single 'name' parameter with 0% coverage in the description. The description does not explain what the parameter represents (e.g., container name or ID), so it fails to compensate for the lack of schema-level descriptions, though the parameter is somewhat self-evident from the tool name.

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 container' is a direct tautology of the tool name, adding no new information about the action's scope or distinguishing it from sibling tools like restart or stop. It communicates a basic action but fails to differentiate the tool from alternatives.

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 provides no guidance on when to use this tool versus alternatives such as podman_container_restart or podman_container_stop, nor does it mention preconditions like the container needing to exist or be in a stopped state.

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