gitea_list_pr_commits

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

With no annotations provided, the description carries the full burden of behavioral disclosure but fails to specify read-only safety, pagination behavior for large commit lists, or error handling when PRs don't exist. 'List all' implies read-only but lacks explicit confirmation.

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 description is brief at one sentence, but includes the '[UNIFIED]' metadata prefix which appears to be implementation noise rather than helpful context. It is under-specified rather than elegantly concise given the lack of schema documentation.

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 4 undocumented parameters, no output schema, and no annotations, the description is insufficient. It omits what the tool returns (commit SHAs, messages, authors, dates?) and how to interpret the results, leaving significant gaps for an AI agent.

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?

The schema has 0% description coverage for all four parameters (site, owner, repo, pr_number). The description provides no compensatory information about parameter formats (e.g., whether 'site' is a URL, what 'owner' refers to) or valid value ranges.

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 tool 'List[s] all commits in a pull request,' specifying the verb (list), resource (commits), and scope (within a PR). However, it does not distinguish from siblings like `gitea_list_pull_requests` (which lists PRs) vs this tool which lists commits within a specific PR.

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?

The description provides no guidance on when to use this tool versus alternatives (e.g., `gitea_get_pull_request` for PR metadata vs this for commit history), nor prerequisites like requiring a valid PR number first.

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