Raw GitLab API request

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

Annotation contradiction: the description allows calling ANY endpoint with methods POST, PUT, PATCH, DELETE per the schema, while annotations declare readOnlyHint=true. The description itself also fails to disclose that operations can modify/delete data, or mention response format, rate limits, or auth details, leaving the contradictory annotation to mislead agents.

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 two sentences, immediately communicates purpose and scope, and includes a link to API resources. Every sentence earns its place, and it is well-structured and front-loaded.

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's generic nature and lack of output schema, the description is too thin. It does not state that responses are raw API JSON, nor does it mention pagination rounding, error handling, or authentication nuances. The link to docs helps, but the contradictory annotation and missing behavioral details leave significant gaps for a tool that can hit any endpoint.

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%, and the description adds no parameter-specific meaning beyond what the schema already documents. The baseline of 3 applies because the schema carries the full burden of parameter semantics.

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 'calls ANY GitLab REST API v4 endpoint with the configured credentials', defining it as a generic raw API tool. It distinguishes itself from siblings by explicitly positioning it as an 'escape hatch' for endpoints 'without a dedicated tool', with examples.

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 explicitly says 'Use it for endpoints without a dedicated tool' and lists example use cases, which is clear when-to-use guidance. It implicitly excludes endpoints with dedicated tools, but does not explicitly name alternatives or state 'do not use when a dedicated tool exists', so it falls short of a 5.

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