github_list_pr_reviews

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

No annotations are provided, so the description carries the full burden. It only states the action without disclosing behavior like pagination, ordering, whether review comments are included, or authentication requirements. The Args list does not add behavioral depth.

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 front-loaded with a one-sentence purpose followed by a compact parameter list. Every element is useful and there is no redundant filler. It is appropriately sized for a simple list operation.

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 availability of an output schema, return-value details are less critical. However, for a list endpoint, the description lacks mention of pagination or any nuances of GitHub PR reviews. It is minimally complete for a simple tool but misses context that would help an agent invoke it reliably.

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 zero description coverage, but the tool description provides an Args section explaining each parameter: owner, repo, pr_number, and session_name. This adds value beyond the schema's type and title, though the explanations are brief and somewhat obvious.

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 states 'List reviews on a pull request,' which is a specific verb and resource. It clearly distinguishes from sibling tools like github_list_pr_files or github_list_issue_comments. The Args section reinforces the target PR context.

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 guidance on when to use this tool versus alternatives. It does not mention exclusions, prerequisites, or similar tools such as github_get_pr or github_list_pr_files. Usage context is only implied by the verb 'list' and resource 'reviews'.

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