Gitea: List pr comments

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

Annotations already declare readOnlyHint=true, so the safety profile is covered and the bar is lower. However, the description adds nothing beyond that — it doesn't say whether pagination applies, whether review/inline comments are included or only issue-style comments, or how many results to expect. The "[UNIFIED]" prefix hints at cross-site behavior but is never explained.

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?

A single short, front-loaded sentence with no wasted phrasing. The unexplained "[UNIFIED]" tag is the only element that doesn't earn its place, and the brevity comes at the cost of substance rather than from tight editing.

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 four-parameter tool with zero schema coverage, no output schema, and no parameter documentation, the description is far too thin. An agent cannot determine what a valid site/owner/repo value looks like or what the response contains without trial and error.

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% across four required parameters (site, owner, repo, pr_number), so the schema contributes no meaning at all. The description only implies that pr_number refers to a pull request; site, owner and repo are left completely undefined, with no format examples or hints about the site identifier.

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?

"List all comments on a pull request" gives a specific verb and resource, and the resource wording implicitly separates it from gitea_list_issue_comments and gitea_list_pr_reviews. The bracketed "[UNIFIED]" tag is unexplained jargon that does not help the agent distinguish anything.

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 when-to-use guidance, no mention of alternatives (e.g. issue comments vs PR review comments), and no prerequisites such as needing read access or a valid pull request index. The agent must infer everything from the tool name.

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