Single tool with significant definition gaps. Tool name 'dynamic_graphql_operations' is generic and does not follow verb_noun pattern (should be 'execute_graphql_operation' or similar). Description is present but vague (58 chars), does not explain WHEN to use it, what it returns, or prerequisites. Input schema is dynamically generated from GraphQL files at runtime; while properties and required fields are constructed, there is no explicit schema validation or documentation of the output structure. Parameters lack individual descriptions, only type hints like 'String array' are provided. No error handling guidance for GraphQL failures. Tool is inferred/dynamic rather than explicitly registered with full metadata.

• Rename tool to 'execute_graphql_operation' or 'query_graphql_api' to follow verb_noun pattern and clarify the action.
• Expand tool description to 100-150 chars: explain that it executes GraphQL queries from the operations directory, when to use it (e.g., 'Use this to fetch data from the configured GraphQL endpoint'), and what it returns (structured JSON data).
• Add per-parameter descriptions in the dynamically generated schema. For each variable extracted from the GraphQL query, include a description field explaining its purpose and constraints.
• Document the output schema in the tool description or return a structured response object with typed fields instead of raw JSON.stringify(). Include pagination guidance if results can be large.
• Enhance error handling to categorize failures (retryable vs. user-fixable) and provide recovery hints, e.g., 'GraphQL query failed: invalid variable type. Check the operation file syntax and variable types.'