Manage Pull Requests

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

Annotations already declare readOnlyHint=false, destructiveHint=false, idempotentHint=false, openWorldHint=true, so the safety profile is covered. The description adds no behavioral context of its own: nothing about merge irreversibility, review side effects, pagination via perPage, or rate limits. For a multi-operation mutation tool this is a real gap beyond what annotations convey.

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?

Two short sentences, front-loaded with the resource and operations. It is well-sized with no filler, though the second sentence largely restates what the action enum already shows.

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?

With 14 parameters, seven dispatchable operations, no output schema, and near-zero schema documentation, the description is far too thin. An agent cannot tell which parameters belong to which action, what a merge response looks like, or how pagination works without guessing.

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 only 7% across 14 parameters, so the description must compensate and it does not. It only mentions `action` (already documented in the schema) and explains nothing about base/head, mergeMethod, commitTitle/commitMessage, event, comments[].path/position, or perPage — leaving most parameters semantically opaque.

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 names the resource (Pull Requests) and enumerates concrete operations (create, get, list, update, merge, list_reviews, create_review), which distinguishes it from sibling tools like manage_issues or manage_milestones. It stops short of 5 because the operation list is essentially a restatement of the action enum rather than a clarification of scope differences.

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?

"Use the `action` field to select the operation" tells the agent how to dispatch among the seven operations, which is useful implied usage. However there is no guidance on when to pick this over siblings, no prerequisites (repo/owner context, auth), and no indication of which parameters are required for which action.

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