createDraftPullRequest

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

No annotations exist, so the description carries the full behavioral burden. It only restates the creation action and does not disclose whether the PR remains unpublished, what 'draft' means in this workflow, or what side effects occur. This is especially ambiguous given the sibling publishDraftPullRequest.

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, short sentence with no fluff, but it is under-specified and mostly restates the tool name. It is concise rather than informative.

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 creation tool with six parameters, no annotations, and no output schema, this description is too minimal. The schema supplies required fields and some parameter descriptions, but the description does not explain how draft PRs behave, when they need publishing, or how this endpoint relates to its siblings.

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?

The description adds no parameter meaning. The schema covers 67% of parameters, but repo_slug and workspace lack descriptions, and the description does not clarify their role, defaults, or relationship to one another.

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 states a clear action and resource: 'Create a draft pull request.' The word 'draft' differentiates it from the sibling createPullRequest, though it does not explicitly contrast against publishDraftPullRequest or convertToDraft.

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?

There is no guidance on when to use this tool instead of createPullRequest, publishDraftPullRequest, or convertToDraft. The description does not mention prerequisites, context, or exclusions, leaving the agent to infer the appropriate scenario.

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