kill_container

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

Annotations already indicate destructiveHint=true. The description adds that it sends a signal (default SIGKILL) and returns the container's attributes. It does not disclose additional behavioral details like prerequisites or side effects, but the annotations lower the bar. Score 3 for moderate 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 concise: one line for purpose followed by a brief parameter list. It is front-loaded with the main action and contains no redundant information. Score 5.

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 is simple with two parameters. The description explains the return value (container attrs). Missing details include prerequisites (container must be running? ) and error conditions, but overall it is fairly complete for a simple signal-sending tool. Score 4.

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?

With 0% schema description coverage, the description compensates by explaining both parameters: 'id_or_name - The container id or name' and 'signal - Signal to send (defaults to SIGKILL)'. This adds meaning beyond the schema types, though it could mention valid signal formats. Score 4.

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 'Send a signal to a container.' This provides a specific verb and resource. However, it does not differentiate from siblings like stop_container or pause_container, which also send signals. Score 4 for clear purpose but lack of sibling differentiation.

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 does not provide any guidance on when to use this tool versus alternatives such as stop_container or pause_container. No when-not-to-use or alternative context is given. Score 2 for no guidance.

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