modal_app_list

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

No annotations are provided, so the description should carry the transparency burden. It discloses the status categories but fails to mention behavior regarding the optional env parameter, pagination, output format, or the meaning of 'recently stopped.' This leaves significant behavioral details undisclosed.

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 sentence that front-loads the action and resource, with no wasted words. It effectively adds the status scope without redundancy or verbosity.

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?

The tool is simple with one optional parameter, but the description does not mention what the list returns or how env affects results. Given the absence of an output schema and annotations, the description is slightly incomplete for guiding a new agent, but the basic purpose is adequately captured.

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 only parameter env is fully described in the schema as 'Environment to interact with,' achieving 100% schema coverage. The tool description adds no additional parameter context, so the baseline score of 3 applies because the schema carries the parameter semantics.

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' plus resource 'Apps' and defines the scope with three statuses, clearly conveying the function and distinguishing it from sibling tools like modal_app_logs or modal_app_stop. The plural 'Apps' and status set make the purpose unambiguous even without explicitly naming alternatives.

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 explicit guidance on when to use this tool versus alternatives such as modal_app_history or modal_app_logs. The intended use is only implied by the action 'List Apps' with specific statuses, so the agent must infer its appropriateness rather than being told.

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