podman_ps

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

The annotations already declare readOnlyHint=true and destructiveHint=false, establishing the safe read profile. The description adds the crucial behavioral trait that only running containers are listed by default and that all=true broadens the result to include stopped ones, which is beyond what annotations provide.

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 two short sentences, front-loaded with the main action '列出 containers' and then elaborating the default and all parameter. Every word earns its place, with no redundant filler.

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 that this is a simple read-only listing tool with an output schema, the description adequately covers the core behavior and the most important parameter (all). It does not explain filters or format, but those are visible in the schema and the read-only nature is annotated, making it complete enough for a basic list operation.

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 input schema has 0% description coverage, leaving the meaning of parameters solely to types and names. The description explains only the 'all' parameter ('all=true 含已停止') but does not clarify 'format' or 'filters', particularly the complex anyOf structure for filters, leaving significant semantic gaps.

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 states '列出 containers' (List containers), which clearly identifies the verb and resource. It further specifies the default scope (only running) and the all=true option to include stopped containers, distinguishing it from inspection or management tools like podman_container_inspect and podman_container_start.

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 provides clear context about the default behavior (listing running containers) and explicitly mentions how to include stopped ones using all=true. While it does not mention alternatives or when-not-to-use, the context is clear enough for basic usage compared to sibling tools.

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