github_repos_merge

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

The description fails to disclose behavioral traits such as required permissions, side effects (e.g., branch deletion, conflict handling), or whether a merge commit is created. With no annotations to supplement, the agent is left uninformed about the tool's impact.

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 very concise (one sentence) but lacks structure or detail. While brevity is valued, it fails to convey essential information, making it average in usefulness.

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 branch merging and the absence of annotations or output schema, the description is severely incomplete. It does not cover prerequisites, error handling, or return values, leaving a significant gap in understanding for an AI agent.

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 input schema has 100% coverage but only provides minimal descriptions ('owner', 'repo', 'Request body (JSON object)'). The 'body' parameter is a loosely typed JSON object with no specification of its required fields (e.g., base, head). The description adds no additional meaning, leaving agents to guess the body structure.

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 'Merge a branch' is extremely brief and fails to specify which branch (source/target) or the context (e.g., merging into the default branch). It does not distinguish itself from sibling tools like 'github_pulls_merge' or 'github_repos_merge_upstream', leading to ambiguity.

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 such as merging via pull requests or upstream merges. The description lacks any context or prerequisites, leaving an AI agent without direction.

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