gitea_list_pr_comments

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

No annotations are provided, so the description carries full burden. While 'List' implies a read-only operation, the description fails to disclose pagination behavior, whether review comments are included, rate limits, or what constitutes 'all' comments.

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 core message is a single efficient sentence, but the '[UNIFIED]' prefix appears to be metadata leakage that adds noise without value. The description is appropriately brief but could front-load more critical information.

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 zero schema coverage, no annotations, no output schema, and four required parameters, the description is insufficient. It fails to compensate for the lack of structured documentation with explanatory context.

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 the description adds no meaning for the four parameters (site, owner, repo, pr_number). Critical details like whether 'site' expects a URL or identifier, or the format of 'owner/repo', are completely absent.

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 clearly states the verb (List) and resource (comments on a pull request), distinguishing it from issue-related tools. However, it does not clarify the distinction from sibling tools like 'gitea_list_pr_reviews' or 'gitea_list_issue_comments'.

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 provided on when to use this tool versus alternatives such as 'gitea_list_pr_reviews' or 'gitea_create_pr_comment'. No prerequisites or contextual conditions are mentioned.

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