boj_github_create_pr

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

No annotations are provided, so the description carries full burden. It only states the action ('Create a pull request') without disclosing behavioral traits like required authentication, rate limits, whether it's idempotent, what happens on failure, or the expected response format. This is inadequate for a mutation tool with zero annotation coverage.

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 with zero waste. It's appropriately sized and front-loaded, though it lacks detail, which is a completeness issue rather than conciseness.

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 the complexity of creating a pull request (a mutation with 6 parameters), no annotations, no output schema, and 0% schema coverage, the description is completely inadequate. It doesn't explain parameters, behavior, or return values, leaving the agent with insufficient information to use the tool correctly.

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 0%, meaning none of the 6 parameters (owner, repo, title, body, head, base) are documented in the schema. The description adds no information about what these parameters mean, their formats, or examples, failing to compensate for the coverage gap.

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 pull request' clearly states the action (create) and resource (pull request), but it's generic and doesn't differentiate from sibling tools like boj_github_merge_pr or boj_gitlab_create_mr. It specifies the GitHub context in the tool name but not in the description.

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 like boj_github_create_issue or boj_github_merge_pr. The description lacks context about prerequisites, such as needing an existing repository or branch, or when this is appropriate in a workflow.

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