shopify_get_metafields

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

No annotations provided, so description must disclose behavior. It correctly indicates a read-only operation and specifies default limit and owner_id requirement. However, it doesn't mention rate limits, pagination, or ordering, which would be helpful for a complete behavioral understanding.

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 concise and well-structured, using a clear header and bullet points for arguments. No unnecessary information, every sentence adds value.

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 tool has an output schema, the description covers all necessary input aspects. It lists all resources, explains parameter requirements, and includes default values. It is complete for a read operation.

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?

With 0% schema description coverage, the description adds essential meaning beyond the schema. It explains each parameter: allowed owner types, required condition for owner_id, namespace as optional filter, and limit range. The note about numeric or GID for owner_id adds clarity.

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 reads metafields from specified Shopify resources, with a list of allowed owner types. This distinguishes it from sibling tools like shopify_update_metafield (write) and shopify_list_metafield_definitions (definitions).

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 explains when to use the tool, including default owner_type, when owner_id is required, and optional filters. It lacks explicit mention of alternatives but contextually distinguishes via purpose.

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