createPullRequest

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

With no annotations, the description is the only source of behavioral context. It only restates the creation action and does not disclose side effects, prerequisites, permissions, or behavior such as default destination branch handling. This is below what is needed 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 short and free of filler, which is good, but it is underspecified for an 8-parameter tool and adds no structure beyond the tool name. It is minimal rather than optimally concise.

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 tool with 8 parameters, no annotations, no output schema, and a closely related draft-PR sibling, a six-word description is inadequate. It omits guidance on repository/workspace needs, default branch behavior, and when the draft variant should be used.

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 75%, so the schema itself documents most parameters well. The description adds no parameter semantics, but the high coverage supports the baseline score of 3.

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 a specific action and object ('Create a new pull request'), clearly identifying the operation. It does not distinguish this from the sibling createDraftPullRequest, so it misses full sibling differentiation.

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 verb 'create' implies this should be used when a new pull request is needed, but there is no explicit guidance about when to prefer it over createDraftPullRequest or when not to use it. No alternatives or exclusions are given.

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