list_cases

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

With no annotations provided, the description carries the full burden of behavioral disclosure. 'List' implies a read-only operation, and the mention of 'mesh and time status' adds useful behavioral context, but it does not explicitly state safety, filtering behavior, or return format. More transparency could be provided.

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, concise sentence that front-loads the main purpose ('List CFD cases') and adds essential detail ('with mesh and time status') without any unnecessary words or repetition.

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 no parameters and an existing output schema, the description is adequately complete. It covers what is listed and the type of status information provided. It lacks explicit usage guidance, but the tool's simplicity and clear purpose make the description sufficient overall.

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 has zero parameters and an empty schema, so there are no parameter details to document. The description's mention of 'workspace' indirectly indicates scope, but it does not add parameter semantics beyond the schema, which is acceptable given the baseline for zero params.

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 the specific verb 'List' and clearly identifies the resource as 'CFD cases in the workspace', adding detail about the included status fields ('mesh and time status'). This distinguishes it from siblings like 'list_templates' (templates vs cases) and 'describe_case' (single case detail vs list).

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 typical usage for listing cases but does not explicitly state when to use it over alternatives or mention any exclusions. It lacks comparative guidance such as 'for details on a single case, use describe_case'.

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