gitlab mcp

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

With no annotations provided, the description carries full burden but reveals almost nothing about behavior. It doesn't mention authentication requirements, rate limits, error handling, whether queries are read-only or can mutate data, or what format the response takes. 'Execute' is vague about the operation's nature and potential side effects.

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, efficient sentence with zero wasted words. It's appropriately sized for a general-purpose tool and front-loads the essential information.

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?

For a GraphQL execution tool with no annotations and no output schema, the description is inadequate. It doesn't explain what types of operations are possible (queries vs mutations), authentication context, error responses, or when to prefer this over specialized sibling tools. The agent would struggle to use this 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 100%, so the schema already documents both parameters fully. The description doesn't add any meaning beyond what's in the schema - it doesn't explain GraphQL query structure, variable usage patterns, or provide examples. Baseline 3 is appropriate when schema does the work.

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 'execute' and the resource 'GitLab GraphQL query', making the purpose understandable. It distinguishes this tool from siblings that perform specific CRUD operations, but doesn't explicitly contrast with other query tools (though none appear in the sibling list).

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 is provided about when to use this tool versus the many specialized sibling tools. The description doesn't indicate whether this is for complex queries not covered by other tools, for custom operations, or when direct GraphQL access is preferred over API endpoints.

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