createDraftPullRequest

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

No annotations are provided, so the description carries the full burden. The description only states the action without disclosing behavioral traits such as that draft PRs are not reviewable, require specific permissions, or can be converted later. Important behavioral context is missing.

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 sentence with no waste, but it is too brief. It lacks important context that could easily be added without making it verbose. It is adequately concise but incomplete.

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 no output schema, no annotations, and 7 parameters, the description is too minimal. It does not cover typical usage context, return values, or behavior differences from siblings. For a tool creating a draft PR, the agent likely needs more context.

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 coverage is 100% (all parameters have descriptions). The tool description adds no additional meaning beyond the schema. Baseline 3 is appropriate as the schema already documents each parameter.

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 new draft pull request' uses a specific verb and resource, clearly distinguishing it from sibling tools like createPullRequest (which likely creates a regular PR) and publishDraftPullRequest (which publishes a draft).

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?

No guidance is provided on when to use this tool versus alternatives. The description does not mention prerequisites, when to prefer draft over open PR, or scenarios where this tool should not be used. Sibling tools like publishDraftPullRequest and convertTodraft exist but no context is given.

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