shopify_graphql_schema

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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and non-destructive behavior, so the description does not need to restate those. It adds a small amount of useful context by scoping the schema to the store API version, which aligns with the open-world hint, but it reveals nothing about output shape or edge behavior.

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 a single front-loaded sentence with no filler or repetition. Every word adds meaning, and the core verb and resource appear immediately.

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?

Given the lack of an output schema, zero parameter documentation, and the presence of closely related query/mutation/validation tools, this description is too thin for an agent to confidently invoke the tool. It does not explain what the returned schema information looks like, how to format type_name, or when this exploration tool is the correct choice over siblings.

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 0%, so the description must compensate for the two undocumented parameters, store and type_name. It does not explain what format store should take, how type_name maps to GraphQL type names, or what happens if the type does not exist. The phrase 'Admin GraphQL schema' weakly implies type_name is a GraphQL type, but that is not enough.

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 names a specific verb ('Explore') and a clear resource (the Admin GraphQL schema) scoped to the store's API version. It is clear enough to distinguish the general intent from query/mutation tools, though it does not explicitly call out sibling alternatives.

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 wording implies this tool is used when you need to inspect or explore GraphQL schema types, but it does not explicitly state when to use it versus shopify_graphql_query, shopify_graphql_mutation, or shopify_validate_graphql_codeblocks. Guidance is only implied, not stated.

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