Scoring was not performed

• Move the GraphQL schema out of the tool description. Instead, store it server-side and reference it as a resource or context. Rewrite execute_query description as: 'Execute a GraphQL query against the connected schema. Introspect the schema first to see available queries and variables.' This keeps the description short (under 120 chars) and token-efficient.
• Add a response schema documentation comment in the tool definition. For execute_query, document that it returns {data: object, errors: [{message: string, ...}]}. For introspection, document the return as a GraphQL introspection result with __schema, types[], queryType, etc.
• Expand the 'variables' parameter description to: 'Optional object of variables to pass to the query. Keys must match variable names defined in the query (e.g., {"id": "123"}). Consult the introspection tool to see available queries and their expected variable shapes.'
• Add a description to the 'query' parameter: 'A valid GraphQL query string. E.g., 'query GetUser($id: ID!) { user(id: $id) { id name email } }'. Introspect the schema first to see supported queries.'
• Expand the introspection description to: 'Retrieve the GraphQL schema to discover available queries, mutations, subscriptions, and their parameters. Call this first when starting a new task, then reference it when composing queries with execute_query. Returns a GraphQL introspection result.'
• Add error handling guidance in the description of both tools. E.g., for execute_query: 'On GraphQL errors, the response includes an errors array with message and path fields. Adjust your query based on the error and retry.'