Execute GraphQL Mutation

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

Adds behavioral details beyond annotations: readonly mode disables tool, modify mode rejects destructive mutation-root fields. Annotations only show readOnlyHint=false and destructiveHint=false, so description adds useful context.

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 brief, front-loaded sentences with no fluff. Every word adds value: clear purpose and key behavioral constraint.

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?

Covers core purpose and behavioral constraints but omits parameter semantics and return value behavior. Adequate for a simple tool but could better leverage parameter descriptions given schema coverage is 0%.

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 0%, but description provides no parameter details or examples. The 'query' and 'variables' parameters are not explained, leaving the agent without guidance on constructing proper mutations.

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?

Description clearly states 'Execute a GraphQL mutation.' with specific verb and resource, and distinguishes from sibling tool gitlab_execute_graphql_query by implying mutations vs queries. Also adds mode-specific behavior.

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?

Provides context on when to use (modify mode, non-destructive mutations) and that readonly disables it, but lacks explicit alternatives or comprehensive when-not-to-use guidance. Implies use gitlab_execute_graphql_query for queries.

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