stop_container

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

Discloses mutating behavior (WRITE), risk level, undo recording, and graceful stop with timeout. However, no permissions or side effects discussed; annotations are absent so description bears full burden.

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?

Very concise: two paragraphs, first stating purpose and key behavior, second listing parameters with defaults. Every sentence is informative, no fluff.

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 simple stop tool with 4 parameters and no output schema, the description covers all needed: action, behavior, args, usage tips. No gaps remain.

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 0%, but description explains all four parameters: container_id (id or name), timeout (seconds, default 10), dry_run (preview), target (from config). Adds essential meaning beyond schema.

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 uses specific verb 'stop' and resource 'container', and contrasts with 'start' (inverse). It clearly distinguishes from sibling tools like start_container, remove_container, restart_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?

Describes when to use dry_run for preview, and mentions undo recording. Provides clear context but does not explicitly state when not to use or list alternatives beyond the inverse.

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