gitee_list_pull_commits

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

Description does not disclose behavioral details like pagination, ordering, or authentication requirements. With no annotations, the description carries full burden for transparency and falls short.

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?

Description is extremely concise (5 words) but still effectively communicates the tool's purpose. Could be slightly expanded but not overly verbose.

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?

Minimal description is adequate for a straightforward listing operation with well-documented parameters, but lacks usage context and behavioral notes, making it merely viable.

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 provides 100% coverage for parameter descriptions (owner, repo, number, page, per_page). Description adds no extra meaning beyond the schema, so baseline score of 3 applies.

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?

Description clearly states the verb 'List' and resource 'commits on a pull request', distinguishing it from sibling tools like gitee_list_commits (likely for all commits) and gitee_list_pulls.

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 explicit guidance on when to use this tool vs alternatives, such as gitee_list_commits for repo-wide commits or gitee_list_pull_files for pull request files.

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