safeoutputs: improve submit_pull_request_review description to prevent empty-invocation ERR_VALIDATION

[Copilot]

Agents were calling submit_pull_request_review with empty arguments {}, triggering ERR_VALIDATION because GitHub rejects contentless reviews with 422. The tool description didn't communicate the body-OR-prior-comments requirement, leaving agents unaware that an empty call is invalid.

Changes

• Top-level description (submit_pull_request_review): Added explicit REQUIRED: constraint stating every call needs either a non-empty body or at least one preceding create_pull_request_review_comment call. Mentions ERR_VALIDATION by name. Adds an inline-only review example to close the ambiguity gap.

• body field description: Replaced the misleading "optional for APPROVE and COMMENT" with the actual invariant — body is only optional when at least one create_pull_request_review_comment was called earlier in the same run; otherwise it is required.

Both the compiler copy (pkg/workflow/js/safe_outputs_tools.json) and the runtime copy (actions/setup/js/safe_outputs_tools.json) are updated identically.

[Copilot]

Pull request overview

Updates the submit_pull_request_review tool description in both the compiler and runtime copies of safe_outputs_tools.json to clarify that a non-empty body or at least one preceding create_pull_request_review_comment call is required, preventing agents from triggering ERR_VALIDATION with empty invocations.

Changes:

• Expanded top-level tool description with explicit REQUIRED constraint, ERR_VALIDATION reference, and an inline-only example.
• Updated body field description to reflect actual invariant (optional only when prior inline comments exist).

Show a summary per file

File	Description
pkg/workflow/js/safe_outputs_tools.json	Compiler-side tool description updated for clearer invocation contract.
actions/setup/js/safe_outputs_tools.json	Runtime-side identical update to keep both copies in sync.

Copilot's findings

Tip

Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

• Files reviewed: 2/2 changed files
• Comments generated: 0