List Merge Request Diffs

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

Annotations already provide readOnly, openWorldHint, idempotent, and non-destructive hints. The description adds little beyond 'detailed diffs and versions/changes view', but does not explain pagination behavior (page, per_page), output format, or whether the diffs are full or summarized. It 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 with no fluff. It is concise but could be more informative without increasing length significantly. No structural issues.

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 5 parameters, no output schema, and 0% schema description coverage, the description is severely incomplete. It does not explain the meaning of 'diffs', the effect of parameters like 'unidiff', or the pagination mechanism. The agent would struggle to use the tool correctly.

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?

The input schema has 5 parameters with 0% description coverage in the schema itself. The description does not mention any parameter, failing to add meaning to 'page', 'unidiff', 'per_page', 'project_id', or 'merge_request_iid'. This is a critical gap for a tool with no output schema.

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 action 'list' and resource 'MR diffs', with the parenthetical 'versions/changes view' adding context. It differentiates from siblings like gitlab_get_merge_request_diffs (which likely returns a single diff) and gitlab_list_merge_request_versions (which lists versions, not diffs). However, it could be more explicit about the exact content returned.

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. For example, there is no mention of when to use this over gitlab_get_merge_request_file_diff or gitlab_list_merge_request_versions. The description lacks any context about prerequisites or typical use cases.

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