Create Merge Request

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

Annotations (readOnlyHint=false, destructiveHint=false, idempotentHint=false) are not contradicted by the description. The description adds the auth requirement, which is a behavioral trait beyond annotations. It does not disclose other potential side effects like triggering CI pipelines or creating comments, so transparency is moderate.

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 sentence of approximately 15 words, front-loaded with the core purpose. Every word is necessary, with no redundancy or fluff.

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 tool's complexity (6 parameters, no output schema), the description is minimal. It covers the core operation and auth requirement but omits information about return values, error conditions, or post-creation effects. Adequate but not complete.

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 coverage is 100% with each parameter having a description. The description does not add additional meaning to the parameters beyond what the schema provides. The mention of authentication is a general requirement, not parameter-specific. Baseline of 3 is appropriate.

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 verb 'Create' and the resource 'merge request', and specifies the context 'in a GitLab project'. It differentiates from siblings by mentioning the requirement for user authentication with write permissions, though it doesn't explicitly distinguish from other creation tools like create_issue.

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 mentions that user authentication with write permissions is required, implying when to use. However, it does not provide explicit guidance on when not to use or suggest alternative tools (e.g., update_merge_request for existing requests). The context is implied but not thorough.

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