list_cases

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

Describes the walk and identification logic, including output format. However, lacks details on performance, symlink handling, error scenarios, and permissions; no annotations to compensate.

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?

Two concise sentences with no wasted words. Front-loaded with action and resource, followed by identification and output details.

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?

Adequate for a simple listing tool with output schema present. However, critical parameter information is missing from both schema and description, reducing completeness.

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 has zero parameter descriptions. Description only indirectly implies search_root is the starting directory and max_depth limits recursion, but does not explicitly define them or their constraints.

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?

Clearly states it walks a directory tree and returns CESM case directories based on a specific identification criterion (CaseStatus file). Distinguishes well from siblings that operate on cases rather than listing them.

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?

Implies usage for finding CESM cases in a filesystem, but no explicit guidance on when to use this tool versus alternatives like get_case_status or specific case operation tools.

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