modal_container_list

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

No annotations are provided, so the description must carry the transparency burden. It discloses that only currently running containers are returned, but does not mention scope behavior (e.g., default environment), pagination, or whether stopped containers are excluded entirely. This is adequate for a low-risk read-only list but lacks deeper behavioral context.

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?

A single, front-loaded sentence with no filler words. It clearly states the action, object, and filter condition, making it highly scannable and appropriately sized for this simple tool.

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 simple list tool with two optional, schema-documented parameters and no output schema, the description is mostly complete. It would benefit from clarifying the default scope when env is omitted, but overall it provides enough information for an agent to select the tool 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?

Schema description coverage is 100%, so the baseline is 3. The description does not add meaning beyond the schema; 'all containers' could be interpreted as global, but the schema already clarifies appId filters to a specific App and env selects environment. No additional parameter context is provided.

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 uses a specific verb ('List') and explicit resource ('all containers that are currently running'), clearly distinguishing it from container exec/logs/stop siblings. The qualifier 'currently running' clarifies the selection criteria.

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 for retrieving running containers, but it does not explicitly state when to use it over alternatives like modal_container_logs or modal_container_stop. There are no exclusions or alternative recommendations, leaving usage to inference.

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