List Merge Requests

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

The annotations already indicate a safe, idempotent read operation. The description adds no behavioral details beyond 'List...' – no mention of pagination, result ordering, or that the tool returns a list. Does not contradict annotations.

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 – very concise. However, it lacks structure or addition of critical details. While front-loaded with the action, it sacrifices necessary information for brevity.

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 has 25 optional parameters, no output schema, and limited annotations, the description is severely incomplete. It fails to mention filtering, pagination, or that the tool returns a list of MR objects. The agent lacks context to use parameters effectively.

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 the description provides no explanation of any of the 25 parameters. Agents must guess parameter meanings from names alone, which is insufficient for a tool with optional filters like `scope`, `state`, `labels`, and `search`.

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 'List' and the resource 'merge requests for a project.' It distinguishes from sibling tools like `gitlab_get_merge_request` (single MR) and `gitlab_list_merge_request_notes` (notes), but it could mention that the tool supports filtering via many parameters.

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 provides no guidance on when to use this tool versus alternatives. For example, it doesn't mention that unlike `gitlab_get_merge_request`, this returns multiple MRs, or how it differs from `gitlab_list_issues`. No context on when filtering is needed.

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