get_latest_result_for_test_case

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

Annotations only supply readOnlyHint=true, but the description adds substantial behavioral context the annotation cannot: the ambiguous semantics of 'latest', live-verified evidence that it means highest id rather than newest date, the 404 condition, and the returned field shape. It also discloses read-back quirks (executionDate mirrors actualEndDate, executedBy duplicated as userKey, automated: true, issueLinks returned as traceLinks).

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?

Front-loaded with the verb, scope and endpoint, and nearly every sentence earns its place by adding non-obvious information. It is long and one clause ('so neither latest by date nor latest by date you set is a safe reading') restates the preceding point, costing a little tightness.

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?

With no output schema, the description carries the burden of explaining return values and does so, enumerating fields and quirks. Combined with the 404 behavior and the ambiguity of the 'latest' selection, an agent has everything needed to call it correctly and interpret the result.

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?

There is a single parameter and schema description coverage is 100%, with the schema already supplying the format example (PROJ-T123). The description adds no additional meaning about testCaseKey beyond what the schema provides, so the baseline 3 applies.

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 ('Read ONE execution of a test case across ALL test runs') and pins it to an endpoint, immediately distinguishing it from get_test_run_results and the run-scoped siblings. An agent can identify the tool's scope 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 explicit when-to-use-this vs when-to-use-an-alternative guidance ('whenever the specific execution matters, read the run with get_test_run_results instead') and names the failure condition (404 when the case has never been executed). This is a textbook routing instruction.

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