get_test_result_issues

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is clear. The description adds nothing about return format or pagination, which is a gap, but the annotations carry the behavioral burden adequately for a read tool.

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 that are front-loaded with the core action. The second sentence is largely redundant with the first, slightly reducing conciseness, but there is no extraneous detail.

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 GET tool with annotations and a single nested parameter, the description is minimally complete. It does not mention pagination or output structure, but the absence of an output schema means the agent has no guidance on the return shape, which is a minor gap.

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% and there is only one nested parameter. The description mentions using the test result's 'unique identifier', which maps directly to testResultId but adds no semantic detail beyond what the schema implies. Baseline for a single undocumented parameter lands at 3.

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 (Get) and resource (issues for a test result), which is clear. It doesn't explicitly differentiate from the sibling get_test_case_issues or get_issue_test_results, leaving some ambiguity about scope, but the resource is identifiable.

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?

No indication of when to use this tool versus the many similar siblings like get_issue_test_results or get_test_case_issues. No prerequisites or exclusions are provided, leaving the agent to infer context.

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