Gitea: List pr commits

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

Annotations already declare readOnlyHint=true, so safety is covered, but the description adds nothing further: no pagination behavior, no ordering guarantees, no statement about how many commits are returned or whether merge commits are included. For a list operation on a potentially large collection, that silence is a real gap.

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 sentence with the core purpose front-loaded; nothing is padded. The only wasted token is the "[UNIFIED]" tag, which conveys nothing to an agent.

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?

With no output schema, no annotations beyond readOnlyHint, and 0% schema description coverage on four required parameters, the description carries the full burden and delivers almost none of it. An agent can guess the intent but cannot determine how to address the repository or what the response contains.

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?

All four parameters (site, owner, repo, pr_number) have zero schema description coverage, and the description never mentions any of them. "Pull request" hints at pr_number, but the site/owner/repo addressing scheme — including what format `site` takes — is completely undocumented anywhere.

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?

States a specific verb and resource ("List all commits in a pull request"), which implicitly separates it from siblings like gitea_list_pr_files and gitea_list_pr_comments. It does not explicitly name or contrast any sibling, and the "[UNIFIED]" prefix is unexplained jargon that adds no meaning.

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 prerequisites, and no mention of alternatives such as listing commits via compare or listing the PRs themselves. The scope (a single PR) is inferable from the resource name but never stated as a usage condition.

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