post_issue_test_results

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

Annotations already declare destructiveHint=true, idempotentHint=false, and openWorldHint=true, yet the description adds nothing about what linking does to an issue's existing test-result associations, whether the operation is reversible, or what permissions are required. For a destructive, non-idempotent mutation this is a substantial omission.

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 short but half of it is redundant: the second sentence repeats the first verbatim rather than adding scope, constraints, or routing information. The space is spent on duplication instead of useful 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 nested, two-parameter destructive mutation with no output schema, the description omits side effects, return behavior, and error conditions. An agent would be guessing about what 'link' actually changes on the issue.

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?

Reported schema description coverage is 0% at the top level, so the description would need to compensate, but it only gestures at 'its unique identifier' — which the schema already spells out as issueId. The body.test_results constraint (which identifier type, acceptable counts) is left entirely to the untyped array items.

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 first sentence names a specific verb and resource (link test results to an issue), so the basic action is identifiable. However, the second sentence merely restates the first with the vague qualifier 'using its unique identifier,' and nothing distinguishes this from the sibling post_test_result_issues, which performs the mirror-image link operation.

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 guidance on when to use this tool versus post_test_result_issues, get_issue_test_results, or delete_issue_test_result. No preconditions (e.g., the issue and test results must already exist, or the caller's permission level) are stated.

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