shopify_validate_graphql_codeblocks

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

Annotations already cover readOnlyHint, idempotentHint, destructiveHint, and openWorldHint, so the safety profile is fully declared. The description adds that validation is performed against 'this store's API version' and that operations are not executed, which adds useful context. However, it doesn't describe the response shape, error behavior, or rate limits.

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?

One sentence, front-loaded, zero waste. States the verb, resource, constraint, and non-execution guarantee in the minimum words needed.

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?

Annotations cover the safety profile and the description covers the non-execution guarantee, but with 0% schema coverage, no output schema, and no guidance on the codeblocks structure or store reference, the definition leaves the agent without the information needed to construct a correct call.

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% and both parameters (store, codeblocks) are undocumented in both schema and description. The nested codeblocks object's fields (content, revision, artifactId) are also unexplained. The description only obliquely references 'operations' without clarifying the codeblock structure's role.

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?

States a specific verb (validate) and resource (Admin GraphQL operations) with the key distinguishing property of not executing. Distinguishes from siblings like shopify_graphql_query and shopify_graphql_mutation, though it doesn't name them explicitly. Sibling differentiation is implied by the 'without executing' clause.

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?

No explicit when-to-use guidance, no alternatives named, no conditions described. The 'without executing them' clause hints at the use case but doesn't state when an agent should choose this over shopify_graphql_query or shopify_graphql_schema.

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