github_pulls_list_review_comments

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

No annotations are given, so the description must disclose behavioral traits. The description only states the action and resource, omitting that this is a read operation, and does not mention pagination, sorting, or any side effects. The agent lacks information about how the tool behaves.

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 very concise (6 words) and front-loaded. However, it is too brief given the tool has 8 parameters and no output schema. Every sentence should earn its place; this one barely provides purpose but lacks detail on usage or behavior. Not overly verbose, but under-specified.

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 tool's complexity (8 parameters, no output schema, no annotations), the description is incomplete. It does not explain the return format, pagination behavior, sorting options, or any constraints. The agent would need to infer or test these behaviors. Schema descriptions mitigate this slightly, but overall context is lacking.

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 input schema has 100% description coverage, so the schema already documents each parameter. The tool description adds no additional meaning beyond the schema. Baseline is 3, and the description does not enhance parameter understanding.

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 action 'List' and the resource 'review comments on a pull request'. However, it does not distinguish from sibling tool 'github_pulls_list_review_comments_for_repo', which lists comments across a repo. A more precise description would mention that comments are for a specific pull request.

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 usage guidelines are provided. The description does not indicate when to use this tool versus alternatives like 'github_pulls_list_review_comments_for_repo' or 'github_pulls_get_review_comment'. The agent receives no context about selection criteria.

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