portainer_containers_list

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

No annotations are provided, so the description carries the transparency burden. It clearly indicates a non-mutating list operation and mentions server-side filtering, but it does not explicitly state that no state changes occur; the verb 'list' strongly implies read-only behavior.

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 compact and well-structured: a one-sentence purpose, a relevant Swarm caveat, and a brief parameter list. There is no redundant or extraneous content.

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 a full output schema exists, the description does not need to detail return fields. It provides enough context for an agent to choose the tool, select an endpoint, apply filters, and understand when to prefer an alternative tool.

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?

All four parameters are described in prose despite the schema having no per-parameter descriptions. endpoint_id's default behavior, show_all's effect, name_filter's substring matching, and stack_filter's exact-match semantics are all clearly explained.

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 operation is to list containers on an endpoint and that the result includes stack and service information. It also distinguishes this tool from container-level actions and from service/stack listing tools by name and intent.

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 explicitly advises preferring portainer_services_list or stack_status on Swarm endpoints, with a rationale that containers are transient task instances there. It also gives practical filter guidance for including stopped containers, filtering by name substring, and filtering by stack.

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