list_test_cases

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

No annotations are supplied, so the description carries the load: it discloses the return surface (rows lack description and steps), the project_id fallback to TESTOPS_PROJECT_ID, and the sort string grammar. It says nothing about pagination behavior or permissions, but for a read-only listing that omission is minor.

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?

Three short sentences, front-loaded with the output shape and followed by routing and parameter hints. No filler, no repetition of what the schema already shows.

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?

An output schema exists, so the description needn't explain return values deeply, yet it helpfully summarizes row fields and their limits. The only gap is pagination semantics for page/size, which an agent would benefit from knowing for large result sets.

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 0%, so the description must compensate: it explains sort syntax with a concrete example ('createdDate,DESC') and the project_id default. It leaves page and size entirely unexplained in both schema and description, so half the parameters remain opaque.

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?

States a specific verb and resource ('List test cases of a project') and pins down the exact row shape returned (id, name, status, automated, flaky, testLayer). It explicitly distinguishes itself from get_test_case and get_test_case_steps, so an agent can route without opening the schema.

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?

Gives clear when-to-use routing: use this for row-level listing, read a single case with get_test_case and its steps with get_test_case_steps. It does not address when to prefer search_test_cases, which is a plausible alternative for filtered lookups, so no exclusion guidance is offered.

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