GitHub app issue-comment tool exposes a PR-only parameter name

Bug description

The model-visible GitHub app tool named github_add_comment_to_issue exposes this required parameter:

pr_number: number // Pull request number in the repository.

The tool name and purpose say it adds a top-level comment to an issue thread, but the required identifier is named and documented as PR-only. This is ambiguous for ordinary GitHub issues and causes agents to either avoid the tool or guess whether an issue number is accepted.

Related GitHub app tools also alternate between repo_full_name and repository_full_name, increasing schema-selection errors.

Expected behavior

Use an issue-compatible identifier such as issue_number, or document that the field accepts both issue and pull-request numbers. Prefer one repository field name across the connector surface where compatibility permits.

Environment

• Codex CLI 0.153.4
• GitHub app tool declaration observed through the model-visible tool inventory

No write operation was executed while reproducing this schema issue.

Start from the model-visible declaration for github_add_comment_to_issue and compare its pr_number and repository field names with the related GitHub app tools. Done means the identifier is clearly issue-compatible or documented for both issues and pull requests, with repository naming made consistent where compatibility permits; verify the exposed tool schemas without executing a write operation.