list_test_run_test_cases

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

No annotations are provided, so the description carries full burden. It mentions 'Public API' which hints at external access, but doesn't disclose critical behavioral traits like authentication requirements, rate limits, pagination behavior, error handling, or whether this is a read-only operation. For a tool with no annotation coverage, this leaves significant gaps.

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, efficient sentence that gets straight to the point. The emoji adds visual distinction but doesn't detract from clarity. It's appropriately sized for a straightforward list operation.

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 read operation with good schema coverage but no annotations or output schema, the description is adequate but incomplete. It specifies the scope ('all Test Cases in a Test Run') but lacks context about authentication, pagination, error scenarios, or relationship to sibling tools. The absence of output schema means the description should ideally hint at return format.

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 100%, so parameters are well-documented in the schema itself. The description adds no additional parameter semantics beyond what's already in the schema descriptions. This meets the baseline expectation when schema does the heavy lifting.

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 clearly states the action ('List all Test Cases') and resource ('in a Test Run from Public API'), making the purpose immediately understandable. It doesn't explicitly differentiate from sibling tools like 'get_test_case_by_key' or 'get_test_cases_by_suite_smart', but the scope is well-defined.

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 provides no guidance on when to use this tool versus alternatives. With many sibling tools for retrieving test cases (e.g., 'get_test_case_by_key', 'get_test_cases_by_suite_smart'), there's no indication of when this list-all approach is preferred or what prerequisites might exist.

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