mergePullRequest

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It discloses signed HTTPS auth, the merge/push process, conditional authorization logic, and optional Nostr events (30618+1631). It also notes the external dependency on git. However, it does not mention failure modes, conflict handling, or side effects on existing refs, leaving some behavioral aspects undisclosed.

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 compact and front-loaded with the core action in a colon-separated phrase. It conveys multiple pieces of information (auth, merge steps, optional events, authorization, dependencies) in just a few sentences without excessive verbosity. Slightly dense but generally well-structured.

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 complex operation with 8 parameters, no output schema, and no annotations, the description covers key aspects: the merge process, authorization rules, prerequisites, and optional parameters. However, it omits details about return values, conflict resolution, and exact effects of the Nostr events. The description is adequate but not fully complete for such a multifaceted tool.

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 63%, so the schema already documents many parameters. The description adds value by clarifying that repoId is optional if derivable from the PR a-tag and implies privkey is used for signed auth. However, it does not explain relays, mergeMessage, or other undocumented parameters, leaving some parameters without semantic enrichment beyond the schema.

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 clearly states the tool's function: 'Full merge: git clone/fetch with signed HTTPS auth, merge PR head, push to bridge, optional 30618+1631.' This specifies the action (merge), the resource (PR), and the process, distinguishing it from siblings like pushToBridge or markPullRequestMerged. The verb 'merge' and the detailed steps leave no 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?

The description provides prerequisites: signer must be repo owner or maintainer, git must be on PATH, and repoId is optional if derivable from the PR a-tag. However, it does not explicitly state when to use this tool instead of related siblings like pushToBridge or markPullRequestMerged. The guidance is implied by the 'Full merge' label but lacks explicit alternatives or exclusions.

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