graphql_query

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It fails to mention that arbitrary GraphQL queries may include mutations (potentially destructive), that the response is raw GraphQL, or any rate limiting/auth requirements. This is a significant gap for a generic execution 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?

The description is two sentences, front-loaded with the core action, and contains no filler. Every word earns its place, making it appropriately concise and well-structured.

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?

The tool is a generic GraphQL executor with no output schema. The description is minimal but sufficient for a simple passthrough tool; however, it omits details about response format and error handling, which would be helpful given the absence of annotations and output schema. It is adequate but not comprehensive.

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?

The input schema provides full descriptions for both 'query' and 'variables', so schema coverage is 100%. The description adds no additional meaning about parameter formats or usage beyond what the schema already states, matching the baseline of 3.

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 tool's function with a specific verb ('Executes') and resource ('arbitrary GraphQL query against the Shopify Admin API'). It also distinguishes itself from siblings by noting it's 'For advanced queries not covered by other tools,' making its purpose unique.

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?

The phrase 'For advanced queries not covered by other tools' provides explicit guidance on when to use this tool versus the many specialized sibling tools. However, it does not name specific alternatives or describe when not to use it, so it falls short of a strong 5.

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