list_containers_simple

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. "List" weakly implies a read-only operation and a collection return, but nothing is said about what "simple" trims from the output, whether the result is paginated, or what fields are included.

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 three-word phrase, which is under-specification rather than conciseness. The parenthetical "(simple)" is filler that occupies space without conveying information the agent can act on.

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 zero-parameter list tool with no output schema and no annotations, the description should at least explain the distinction from list_containers and what the "simple" variant returns. Neither is present, so an agent has no basis for choosing between the two sibling tools.

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 tool takes zero parameters and the schema is empty, so there is no parameter semantics to document. Baseline of 4 applies for a no-argument tool; the description neither adds nor omits anything meaningful here.

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 core verb+resource ("List containers") is identifiable, but the qualifier "(simple)" is never explained, so the agent cannot tell what makes this variant simple. A sibling named list_containers exists and the description makes no attempt to differentiate the two, leaving the purpose only partially resolved.

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?

There is no indication of when to use this tool instead of list_containers, list_containers_by_image, or any other listing sibling. No prerequisites, no scope conditions, no exclusions — the agent must guess.

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