Get Shopify Metafields

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

Annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint, so the safety profile is covered. The description adds genuine value with the per-resource-type scope requirement for read access, but says nothing about pagination, limits, or what an empty result means.

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?

Two sentences, no filler, with the core action front-loaded and the permission requirement immediately after. Every clause carries information an agent needs.

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 simple three-parameter read tool with rich annotations and no output schema, the description covers purpose, scope, and access requirements adequately. The remaining gap — return shape and pagination behavior given the limit parameter — is minor since annotations carry the safety profile.

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 coverage is 67%: ownerId is well documented as a GID with resource examples and namespace as a filter, while limit is only constrained numerically with no description. The description adds no parameter-level meaning beyond the vague 'any Shopify resource' hint, so the schema does the heavy lifting — a baseline 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?

States a specific verb and resource ('Get metafields') and adds useful scope ('for any Shopify resource'), so an agent knows it retrieves rather than writes. It does not, however, differentiate itself from the nearby shopify_set_metafield / shopify_delete_metafield siblings, leaving that routing to inference from the verb alone.

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 description supplies a real prerequisite ('Requires read access on the owner resource type, e.g. read_products for product metafields'), which is actionable context. It gives no explicit when-to-use versus the set/delete metafield siblings and no exclusions, so guidance is implied rather than stated.

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