container_action

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

No annotations provided; description lists actions but fails to disclose behavioral traits such as destructiveness of 'remove', need for permissions, or side effects like data loss. Transparency is minimal.

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?

Single sentence with 10 words, completely front-loaded. Every word is necessary and earns its place. Highly concise.

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 tool with 4 parameters and 6 actions, including destructive ones, the description lacks completeness. Does not warn about irreversible removal or note that timeout applies only to stop. No output schema to supplement.

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?

Schema has 100% description coverage, so the description adds no new meaning beyond what the schema already provides (e.g., action enum, timeout, force). Baseline score of 3 is appropriate.

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?

Description clearly states the tool performs container lifecycle actions (start, stop, restart, etc.), with a specific verb and resource, differentiating it from sibling tools like container_create or container_logs.

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?

Usage is implied by listing actions, but no explicit guidance on when to use this tool versus alternatives (e.g., use container_create for new containers) or when not to use it.

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