create_merge_request

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

Annotations already indicate readOnlyHint=false (mutation), and the description reinforces this with 'Create'. The dry_run default and its proper use (set to false only after confirmation) are transparently stated. However, the tool's post-creation behavior (e.g., return value, side effects) is not described, though the schema covers parameters well.

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: two sentences that state the purpose and a key behavioral note (dry_run default). No unnecessary words or redundancy. It is front-loaded and efficient.

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?

Despite the detailed input schema and annotations, the description lacks essential context about the creation process: what the tool returns (specifically, no output schema), potential side effects, error conditions, or prerequisites (e.g., source branch must exist, permissions). For a complex operation with 10 parameters, the description is incomplete.

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 100%, so the schema already documents all 10 parameters adequately. The description adds only the dry_run default behavior, which is already present in the schema. No additional meaning beyond the schema is provided.

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 action 'Create' and the resource 'merge request', and distinguishes it from sibling tools like update_merge_request or merge_merge_request by its creation nature. The default dry_run behavior is also noted, adding precision.

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 and schema provide clear guidance on dry_run mode, including the default and when to set to false (only after user confirmation). However, it does not explicitly mention when to use this tool versus alternatives like update_merge_request or merge_merge_request, though the creation intent is implied.

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