gitlab_raw_api

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

Annotations supply only readOnlyHint=false; the description adds the important trait that this tool performs no validation and forwards a wrong path or field verbatim to the instance. It does not mention auth requirements, rate limits, or that non-GET methods mutate state (only implied by the method enum), so it stops short of full disclosure.

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?

Two tight sentences with no filler; the escape-hatch purpose comes first and the routing warning is front-loaded immediately after it.

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?

An output schema exists, so return values need no explanation, and the description covers purpose, alternatives, and the main risk. It leaves unstated who may call it and what permissions each HTTP method requires, a minor gap for an unvalidated write-capable tool.

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 75% and the schema already documents path format, query stringification, and body shape. The description adds the pass-through/no-validation semantics for all parameters but no per-parameter syntax or constraints, so baseline 3 applies.

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?

States a specific verb and resource ('call any API v4 endpoint directly') and frames it as the escape hatch for endpoints without dedicated tools, naming concrete example domains. An agent can distinguish it from the ~30 dedicated gitlab_* siblings at a glance.

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?

Gives both sides of the routing decision: use this when no dedicated tool exists, and 'Prefer a dedicated tool when one exists.' That is an explicit when-not plus an alternative-selection rule, which is exactly what usage guidance should do.

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