github_pulls_create_review

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

With no annotations, the description must disclose behavioral traits. It implies mutation but does not explain that creating a review can be pending or submitted depending on the body content, nor that it requires write permissions. The tool modifies pull request state, which is not mentioned.

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 sentence, which is concise, but it is too brief to provide necessary details. It sacrifices completeness for brevity.

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 complexity of the input schema (nested `body` object) and the presence of many sibling tools, the description is incomplete. It does not explain return values (no output schema) or how to correctly structure the body parameter. An agent would likely struggle to use this tool correctly.

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% coverage but only minimal descriptions (e.g., 'owner', 'repo', 'Request body (JSON object)'). The tool description adds no further meaning, especially for the `body` parameter which is a complex object. The agent is left guessing what properties the body should contain.

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 'Create a review for a pull request' clearly states the action and resource. However, it does not differentiate this tool from sibling tools like `github_pulls_submit_review` or `github_pulls_create_review_comment`, which could cause confusion.

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 `github_pulls_submit_review` or `github_pulls_create_review_comment`. The description lacks context about prerequisites or conditions for use.

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