create_pr_review

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

No annotations are provided, so the description must convey behavioral traits. It is a single line stating only the action, with no disclosure of side effects, required permissions, or whether it can overwrite existing reviews. This is insufficient for a mutation 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 one sentence with no wasted words. However, given the tool has six parameters and a nested object, a slightly longer description with key details would improve usability without sacrificing conciseness.

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?

The description is drastically under-specified for a creation tool with six parameters, an enum, and a nested object. It omits context about the event types, the relationship between 'body' and 'comments', and the requirement for the PR to exist. The lack of an output schema makes this even more critical.

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?

All six parameters have descriptions in the input schema (100% coverage), so the schema already documents them. The description adds no extra meaning beyond what the schema provides, achieving the baseline score.

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 verb 'Create' and the resource 'a review on a pull request'. The tool name further reinforces this, making it easy to understand the tool's purpose and distinguish it from siblings like 'get_pr_reviews' or 'edit_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?

The description provides no guidance on when to use this tool versus alternatives (e.g., 'list_pr_reviews', 'edit_pull_request', or 'request_pr_review'). It lacks any mention of prerequisites, constraints, or context that would help an agent decide to invoke this tool.

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