get_test_cases_linked_to_issue

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

Goes well beyond the readOnlyHint annotation: it discloses that the result is one entry per LINK (duplicates possible), that ordering is unstable and de-duplication by key is required, and that lastTestResultStatus is a denormalized value with specific staleness semantics after run deletion. This is exactly the kind of behavioral context annotations cannot carry.

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?

Purpose and routing are front-loaded in the first sentences, and the return-value caveats follow in a logical order. It is dense and long, but nearly every sentence carries distinct, non-redundant information; only slight trimming of the lastTestResultStatus explanation would improve it.

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 fully compensates by describing the return shape (array of test case objects, per-link entries), duplicate/order behavior, and the semantics of the key status field. An agent has everything needed to call and interpret the tool.

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 coverage is 100% and the single issueKey parameter is already documented with an example format in the schema. The description references the key only via the endpoint path and adds no new meaning beyond what the schema provides, so the baseline of 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+resource ('List the test cases linked to a Jira issue'), gives the underlying endpoint, and frames the purpose as requirement/bug-to-test traceability. It clearly distinguishes itself from link_issues_to_test_cases (creation) and get_issue_test_coverage (execution-aware variant).

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?

Explicitly names the alternatives and the conditions selecting them: use link_issues_to_test_cases or the issueLinks field of create_test_case to create links, and use get_issue_test_coverage to also see the latest execution of each case. It even states when the distinction matters (denormalized vs live execution resolution).

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