create_pull_request_review

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. 'Create a review' implies a write operation that likely requires permissions and affects pull request status, but the description doesn't mention authentication needs, rate limits, side effects (e.g., notifications), or what happens on success/failure. For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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, efficient sentence with zero waste—'Create a review for a pull request' is front-loaded and directly states the action. Every word earns its place, making it easy to parse quickly without unnecessary elaboration.

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 (7 parameters, mutation tool) and lack of annotations or output schema, the description is incomplete. It doesn't cover behavioral aspects like permissions, side effects, or return values, leaving gaps for the agent to infer. For a tool that creates reviews—a potentially impactful operation—more context is needed to ensure correct usage.

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 100%, so the schema already documents all 7 parameters thoroughly (e.g., 'owner', 'event' with enum values). The description adds no additional meaning beyond the schema—it doesn't explain parameter relationships, defaults, or usage examples. Baseline 3 is appropriate when the schema does the heavy lifting, but the description doesn't compensate or enhance 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 'Create a review for a pull request' clearly states the verb ('create') and resource ('review for a pull request'), making the purpose immediately understandable. It distinguishes from sibling tools like 'submit_pull_request_review' (which likely finalizes a review) and 'dismiss_pull_request_review' (which removes one). However, it doesn't specify what a 'review' entails (e.g., approval, comments, changes), which keeps it from a perfect score.

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. It doesn't mention prerequisites (e.g., needing pull request access), differentiate from similar tools like 'add_issue_comment' or 'submit_pull_request_review', or specify contexts (e.g., code review workflows). Without any usage context, the agent must infer from the name and schema alone.

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