lattice_stop_container

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

No annotations provided, so the description must disclose behavioral traits. It only mentions 'running container' but fails to explain what 'stop' entails (e.g., container state changes, if it can be restarted, idempotency, or side effects like network disconnect).

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 at five words, but it lacks necessary detail to be maximally useful. While it is concise, it does not fully earn its place because crucial context about the action's meaning is missing.

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 the absence of an output schema and the existence of many sibling container lifecycle tools, the description is incomplete. It does not explain the tool's exact effect (graceful stop vs force kill), return value, or prerequisites for use.

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 coverage is 100% with a clear description 'Container ID' for the required 'id' parameter. The description adds no additional semantic value beyond the schema, so 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?

The verb 'Stop' and resource 'container' clearly state the action. However, it doesn't distinguish from sibling tools like 'lattice_kill_container' (forceful stop) or 'lattice_pause_container' (temporary pause), which have similar purposes.

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 on when to use this tool vs alternatives (e.g., kill, pause, restart). No prerequisites or context about the container's state (must be running) is stated beyond the description itself.

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