lattice_kill_container

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

The description says 'Force kill' implying abrupt termination without cleanup, but does not disclose specific consequences (e.g., data loss, connection drops) or required permissions. Without annotations, this leaves significant behavioral ambiguity for a destructive action.

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 a single sentence, which is concise but lacks front-loaded critical information. It does not waste words but is under-specified, missing context that would make it more helpful.

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 destructive operation with no annotations, output schema, or return value description, the description is insufficient. It omits effects, prerequisites, and outcome details, making it incomplete for informed 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% and the description adds no extra meaning beyond what the schema already provides for 'id'. Baseline score of 3 applies.

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 the action (Force kill) and resource (container). It is specific and distinguishes from stop or remove, though not explicitly differentiated from sibling tools like lattice_stop_container or lattice_force_remove_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?

No guidance on when to use this tool versus alternatives such as stop or force_remove. No prerequisites or exclusions mentioned.

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