get_test_case_test_runs

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

Annotations already declare readOnlyHint=true, idempotentHint=true, destructiveHint=false, so the safety profile is fully covered without the description. The description adds only the traversal semantics (runs containing the case); it says nothing about pagination, result volume, or ordering, which are the traits an agent would still want for a collection endpoint.

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 short sentences, front-loaded with the purpose. The second sentence largely restates the first ('get all test runs for a test case' vs 'retrieve all test runs that include a specific test case') with only the relation direction as new information, so there is mild redundancy but no bloat.

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 single-parameter, read-only lookup with no output schema, the definition covers the essentials. Missing are the things that matter for a collection endpoint — return shape, pagination, and how it differs from the sibling test-result endpoints — leaving it adequate but not complete.

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% at the top level (a single nested 'path' object), though the inner testCaseId carries its own description. The description adds only 'using its unique identifier', which restates the schema rather than explaining the nested path wrapper or the identifier's provenance.

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 ('Get all test runs for a test case') and clarifies the relation direction — test runs that *include* a given test case. This implicitly distinguishes it from its near-namesake sibling get_test_case_test_results (results, not runs) and from the reverse lookup get_test_run_test_cases, though it never names 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?

Usage is only implied: the phrase 'test runs that include a specific test case' tells the agent the relation being traversed, which is enough to know roughly when it applies. But there is no explicit when-to-use guidance, no mention of the adjacent get_test_case_test_results / get_test_run_test_cases alternatives, and no stated prerequisites.

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