Gitlab Graphql

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

No annotations exist, so the description carries the full behavioral burden. Saying 'mutations' hints at write capability, but nothing discloses permission/scopes needed, whether destructive mutations are permitted, rate limits, error or partial-error handling, or pagination behavior — all critical for a raw query tool.

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?

A single front-loaded sentence with no filler. It is efficient, though its brevity is partly the source of the missing guidance rather than a virtue in itself.

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 raw GraphQL executor with no annotations and no output schema, the description should explain how to discover the schema (the discover_graphql_schema sibling), how variables and operation_name interact, and what the response looks like. None of that is present.

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 each parameter (query, variables, operation_name) is already documented in the schema. The description adds no syntax, format, or example detail beyond that, which is the baseline case when the 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?

Specific verb+resource: 'Execute raw GraphQL queries and mutations ... on GitLab' clearly identifies what the tool does. However, it does not differentiate itself from the many specialized siblings like gitlab_graphql_ops_update_merge_request or gitlab_discover_graphql_schema, which also speak GraphQL.

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 at all on when to use this generic escape hatch versus the purpose-built gitlab_graphql_ops_* tools, the REST-level api_request/gitlab_api_request, or gitlab_discover_graphql_schema for schema lookup. The agent must infer the selection criteria from sibling names alone.

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