boj_gitlab_create_mr

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. It only states the action ('Create') without any details on permissions required, side effects, error handling, rate limits, or what the tool returns. This is inadequate for a mutation tool with zero annotation coverage.

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 extremely concise with just three words, front-loaded with the core action. There is no wasted language, though this brevity contributes to the lack of detail in other dimensions.

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 creating a merge request (a mutation operation), the absence of annotations and output schema, and 0% schema description coverage, the description is completely inadequate. It provides no behavioral context, parameter guidance, or usage instructions, leaving critical gaps for an 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?

Schema description coverage is 0%, meaning none of the 4 parameters (project_id, title, source, target) are documented in the schema. The description adds no information about what these parameters mean, their formats, or how they interact, failing to compensate for the schema gap.

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 'Create a merge request' clearly states the action (create) and resource (merge request), but it's vague about scope and lacks differentiation from sibling tools like 'boj_gitlab_create_issue' or 'boj_github_create_pr'. It doesn't specify what system or context this applies to beyond the tool name hinting at GitLab.

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. There are multiple sibling tools for creating items (e.g., 'boj_gitlab_create_issue', 'boj_github_create_pr'), but the description offers no context, prerequisites, or comparisons to help an agent choose appropriately.

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