Resolve Merge Request Thread

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

Description merely restates the action, adding no additional behavioral context beyond annotations. Annotations already indicate non-read-only and non-destructive, but description omits side effects, reversibility, or authorization needs.

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?

Very concise single sentence but at the expense of necessary details. Front-loaded but insufficient for effective tool usage.

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?

Lacks output schema, does not explain parameter relationships or data sources. Incomplete for a tool modifying merge request discussions, missing how to get discussion_id and note_id.

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%, and description does not explain any parameters. While 'resolved' boolean is implied, no clarification on note_id vs discussion_id, project_id, or how to obtain them.

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?

Description clearly states the tool resolves/unresolves an MR discussion note, using specific verb and resource. It distinguishes from siblings like gitlab_create_merge_request_thread and gitlab_update_merge_request_discussion_note.

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, no prerequisites or context for resolve vs unresolve, no mention of permissions or required state.

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