podman_container_stop

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

The description discloses the timeout behavior (default 10 seconds then SIGKILL), which goes beyond the annotations' idempotent/destructive hints. It adds context about how the stop process executes but doesn't mention other side effects.

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 concise sentence that front-loads the primary action. It is efficient and without filler, though it omits some contextual details such as usage guidance.

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 tool's simplicity, the annotations (idempotent, non-destructive), an existing output schema, and the timeout behavior description, the description is mostly complete. It lacks usage guidance but covers the essential behavioral detail.

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 fails to compensate for parameter explanations. It indirectly references the timeout default but does not explicitly link it to the timeout parameter or explain the name parameter beyond the 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?

The description clearly states the action 'stop container' with a specific resource (container). The additional detail about SIGKILL after 10 seconds further clarifies the behavior, distinguishing it from start/restart siblings.

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 implies the tool is used to stop a container but provides no explicit guidance on when to use it versus alternatives like podman_container_start or podman_container_restart. No exclusions or alternative tool references are mentioned.

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