list_pull_request_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 of behavioral disclosure. The description only states what the tool does ('list reviews') with no mention of pagination, ordering, return shape details, or what a review record contains (comments, states, etc.). For a list operation, the agent gets no expectation of what the result set looks like.

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?

A single concise sentence with no wasted words. It's appropriately short for a simple list operation, though the brevity comes at the cost of missing useful guidance.

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?

Despite an output schema existing, the description is thin for a tool in a large GitHub PR toolset (17 siblings). With zero annotations and zero parameter descriptions, the description should provide more context about review types, pagination, or the distinguishing purpose. The complejsoness is minimal for the given context complexity.

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 description coverage is 0%, meaning the input schema has no descriptions. The description doesn't clarify the parameters either — it never mentions that repo/owner/pull_number identify which pull request's reviews to fetch. The 'owner' parameter has a default of empty string, and no clarification of whether it's required alongside repo. The description adds no meaning beyond names.

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 the verb and resource ('List reviews for a pull request'), which is clear. However, it doesn't distinguish itself from closely related siblings like get_pull_request, list_pull_request_files, and preview_pull_request, so differentiation among the GitHub PR toolset is missing.

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 like get_pull_request or preview_pull_request. The description gives no context about when listing reviews is appropriate or any exclusions.

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