gitee_list_issue_comments

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

With no annotations, the description carries full burden for behavioral disclosure. It only states 'List comments on an issue' without revealing traits like ordering, pagination behavior, authentication needs, or that it is a read-only operation. This is insufficient for a list tool.

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 a single concise sentence. However, it is too brief and lacks structure; it could include more information (e.g., scope of listing, return format) without being overly long.

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 the lack of output schema and the presence of 5 parameters (including pagination), the description is incomplete. It does not mention that the tool returns a paginated list of comment objects, leaving the agent without expectations on the response format.

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?

Input schema has 100% coverage; all parameters (owner, repo, number, page, per_page) are described. The description adds no additional semantic meaning beyond what the schema already provides, meeting the baseline but not compensating for low coverage.

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 'List comments on an issue' clearly states the verb (list) and resource (comments on an issue), distinguishing it from tools like gitee_list_issues or gitee_list_repo_issue_comments, though it does not explicitly call out differences.

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 is provided on when to use this tool versus alternatives such as gitee_get_issue_comment for a single comment or gitee_list_repo_issue_comments for all comments in a repository. There is no mention of context or exclusions.

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