portainer_containers_list

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

No annotations are provided, so the description must disclose behavior. It mentions the default behavior for endpoint_id, the effect of show_all, and the server-side nature of name_filter. However, it does not mention pagination, rate limits, or authentication requirements, which are relevant for a listing operation.

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 brief and front-loaded with the main action. The parameter list is clear and uses bullet points for readability without any wasted sentences.

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 (3 parameters, no nested objects), the description covers the key behavioral aspects. An output schema is present to document return values, so the lack of return value explanation is acceptable. It is complete enough for an agent to use correctly.

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 (only titles), so the description carries the full burden. It explains each parameter's purpose and default behavior, adding meaningful context beyond what the schema provides.

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 'List containers on an endpoint' with a specific verb and resource. It clearly distinguishes from sibling container operations like exec, inspect, logs, etc.

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 context for each parameter, such as endpoint_id defaulting to a default endpoint, show_all for including stopped containers, and name_filter for server-side substring filtering. It lacks explicit when-to-use compared to alternatives, but the purpose is clear enough for an agent to select appropriately.

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