github_merge_pull_request

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

No annotations are provided, so the description bears full responsibility for disclosing behavior. It fails to mention that merging a pull request is a destructive/write operation, any required permissions, or side effects. The description focuses on routing details irrelevant to behavioral transparency.

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 short but wastes space on generic routing information ('Routes through /api/tools/invoke...') that is likely common to all tools in this context. It could be more concise and focused on the merge operation.

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 that merging a pull request requires specifying which PR and repository, and the tool has no output schema details, the description provides no actionable information for the agent. It is grossly incomplete for a nontrivial operation.

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 single parameter 'arguments' has a type and default documented in the schema, but the description adds no insight into what arguments are needed (e.g., PR number, merge strategy). With 0% schema description coverage, the description should compensate but only repeats that it's a JSON string.

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 merely restates the tool name ('Github connector operation merge_pull_request') without explaining that it merges a pull request on GitHub. It adds no verb or resource context beyond the name.

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 on when to use this tool versus alternatives like github_create_pull_request or github_update_pull_request. No context about prerequisites or typical scenarios.

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