update_merge_request

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

Annotations indicate readOnlyHint=false, consistent with a mutation. The description discloses that dry_run is enabled by default for safety, adding behavioral context beyond annotations. It does not detail permissions or side effects, but the dry_run note is valuable.

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, efficient sentence that conveys the purpose and a critical behavioral detail (dry_run) without unnecessary words.

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?

With 10 parameters fully described in schema and no output schema, the description covers what is updated and the dry-run default. It is adequate for the tool's complexity, though it could mention that dry_run shows a preview.

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%, so the schema already documents all parameters. The description lists the main updatable fields but adds no new semantic meaning beyond the schema's descriptions.

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 it updates a merge request, listing specific fields (title, description, labels, assignees, reviewers). The verb 'Update' and resource 'merge request' are precise, and it distinguishes from siblings like create_merge_request or merge_merge_request.

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 dry_run=true by default, which guides safe usage. However, it does not explicitly state when to use this tool versus alternatives like update_issue or approve_merge_request, though the context implies it.

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