get_issue_test_results

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

Annotations already declare readOnlyHint=true, idempotentHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is fully covered elsewhere. The description adds nothing beyond that — no note on pagination, empty-result behavior, or permissions — and the second sentence merely restates the first. It is redundant rather than enriching.

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 purpose is front-loaded in the first sentence, which is good, but the second sentence is a near-verbatim restatement ('Retrieve all test results linked to an issue using its unique identifier') and earns no place. Net effect is a two-sentence description carrying one sentence of information.

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 simple read-only lookup with full annotation coverage and no output schema, the minimum is met: the agent knows what it fetches and that it is safe. What is missing is disambiguation from the sibling test-result tools and any note on the nested path parameter or result shape, which are the remaining gaps an agent would hit.

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 reported as 0%, so the description should carry the burden of explaining the nested 'path.issueId' structure. It only says 'using its unique identifier', which confirms that the issue's identifier is required but adds no format, type, or nesting detail beyond what the schema already conveys.

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 states a specific verb and resource ('Get all test results linked to an issue'), which is unambiguous on its own. It does not, however, distinguish itself from closely related siblings such as get_test_case_test_results, get_test_run_test_results, or the inverse get_test_result_issues, so the agent must infer the difference from the name alone.

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?

There is no explicit guidance on when to use this tool versus the many sibling test-result queries (by test case, by test run, or the reverse get_test_result_issues). The only usage signal is implicit in the phrase 'linked to an issue', which gives context but no exclusions or alternatives.

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