manage_pull_requests

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

With no annotations provided, the description carries the full burden of behavioral disclosure. While it lists the available actions, it provides no information about authentication requirements, rate limits, side effects, error conditions, or what happens when operations succeed/fail. For a tool with 11 different mutation actions (create, update, merge, approve, etc.), this lack of behavioral context is a significant gap.

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 that packs substantial information by enumerating all 11 supported actions. It's appropriately front-loaded with the core concept ('unified tool covering all pull request operations') followed by the action list. While dense, every word earns its place by specifying scope.

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?

For a complex tool with 11 different actions (many being mutations), no annotations, and no output schema, the description is incomplete. It doesn't address authentication needs, error handling, response formats, or the behavioral differences between actions like 'merge' versus 'decline'. The agent lacks crucial context to use this tool effectively across its varied operations.

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 16 parameters thoroughly. The description adds no additional parameter semantics beyond what's in the schema - it doesn't explain parameter relationships, constraints, or usage patterns. The baseline of 3 is appropriate when the schema does all the parameter documentation work.

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 tool's purpose as a 'unified tool covering all pull request operations' and enumerates the 11 specific actions it supports (list, get, create, update, merge, approve, unapprove, decline, diff, diffstat, commits). This provides a comprehensive verb+resource scope and distinguishes it from sibling tools like manage_pr_comments which would handle only comments.

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, explain why one would choose this unified tool over more specialized siblings, or indicate which actions require specific permissions or conditions. The agent must infer usage entirely from the action parameter.

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