shopify_graphql_schema

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and non-destructive, so safety is covered. The only extra hint is 'this store's API version' (schema varies by version), but there is no word on what is returned (SDL text, type list, field metadata) or how it behaves for unknown type names.

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?

A single, front-loaded sentence with no filler. It is efficient, though the brevity here reflects under-specification as much as tight writing.

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?

For a read-only introspection tool with annotations covering safety and no output schema, the description still omits the two things the agent most needs: what type_name refers to and what the call returns. It is too thin given 0% parameter coverage.

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 both required parameters are undocumented. The description implies type_name is a GraphQL schema type but never says so explicitly, nor does it clarify the store identifier's format — a significant gap for a tool whose core input is a type name.

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 pairs the verb 'Explore' with the resource 'Admin GraphQL schema' and scopes it to the store's API version, which is slightly more than the name alone. However, it does not distinguish itself from near-siblings like shopify_graphql_query, shopify_graphql_mutation, or shopify_describe_action, so the agent must infer that this is introspection rather than execution.

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?

There is no guidance on when to reach for schema exploration versus running a query or calling describe_action, and no mention of prerequisites. An agent gets no routing signal.

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