stop_container

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It merely restates the action without explaining side effects, whether a force shutdown occurs, or any system impact. The schema hints at a timeout for force shutdown, but the description omits this important behavioral context.

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 excessively terse—only three words—and is under-specified rather than genuinely concise. It fails to include any contextual info, making it closer to a tautological label than an effective description.

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 description is incomplete for a tool with close siblings and no annotations. It does not explain what 'stop' entails (hard stop vs graceful shutdown), when to use it, or the meaning of the timeout parameter. This falls below the minimum viable level for an operation with such ambiguity.

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 provides complete descriptions for all three parameters (node, vmid, timeout), achieving 100% coverage. The description adds no additional param meaning, which is acceptable given the schema already documents them thoroughly.

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 'stop' and the resource 'container', making the basic purpose identifiable. However, it does not distinguish this from closely related sibling tools like shutdown_container or restart_container, so it lacks full clarity regarding what specific behavior 'stop' implies.

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 is provided on when to use this tool versus alternatives such as shutdown_container (typically a graceful shutdown) or start_container. The description gives no context or exclusions, leaving the agent without criteria for selecting this tool over its siblings.

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