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

The readOnlyHint annotation already communicates safety, and the description's 'List' wording is consistent with a read-only operation. It reveals the main behavioral nuance (fetching full details with testCaseId) but does not mention edge cases like pagination limits or errors from missing 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?

The description is concise, uses only two sentences, and front-loads the primary purpose. It adds the alternative behavior without unnecessary 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?

Given the absence of an output schema, the description gives enough context to understand both the list and single-case behaviors. It notes the required project context, though it could be slightly more explicit about the response shape for the list case.

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?

All four parameters are fully described in the schema, and the description adds important relationships: testSuiteId is required unless testCaseId is given, and testCaseId returns the full case with request config, assertions, and response extractions. This exceeds the baseline for schema-covered parameters.

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?

Description clearly states the tool lists test cases of a suite in execution order, and also explains the alternate behavior when testCaseId is supplied. It is easy to distinguish from sibling tools like list_test_suites.

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?

Provides clear usage guidance: pass testSuiteId to list cases, or pass testCaseId to retrieve a single full case, in which case testSuiteId is not needed. It also notes project context is required, though it does not explicitly contrast with every sibling alternative.

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