post_test_result_issues

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

Annotations declare destructiveHint=true and readOnlyHint=false, indicating a mutating operation. The description adds no behavioral context: it does not state whether linking replaces existing links, whether it requires specific permissions, or what happens on failure. With annotations covering the safety profile, a 2 reflects that the description contributes no extra behavioral insight.

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 description is two sentences that are essentially duplicative ('Link issues to a test result' repeated). It is concise but the second sentence adds no new information beyond the phrase 'using its unique identifier,' which is somewhat helpful but poorly integrated. Front-loading is adequate.

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?

Given the tool's mutation nature (destructiveHint=true), nested object parameters, and no output schema, the description is insufficient. It omits critical details such as the expected format for issue identifiers, whether linking is idempotent, and any side effects. For a destructive tool with complex parameters, this is a significant 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%, so the description must compensate for undocumented parameters. It mentions 'using its unique identifier' but does not explain the nested body.issues array or clarify what identifiers are expected (e.g., issue IDs vs. keys). This leaves required parameters undocumented in both schema and description.

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: 'Link issues to a test result.' It clearly identifies the action and target object, distinguishing it from sibling tools like get_test_result_issues (read). However, it does not differentiate from other linking tools such as post_issue_test_results, which achieves the inverse relationship.

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 guidance is provided on when to use this tool versus alternatives like post_issue_test_results or delete_issue_test_result. The description gives the purpose but no context, prerequisites, or exclusions.

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