list_product_metafields

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

No annotations are provided, so the description carries the full burden. It mentions the GraphQL interface and that it returns specific fields, but does not disclose pagination behavior, default limit, or read-only nature. The description says 'List all metafields' which may be misleading given the limit parameter.

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 concise sentences that front-load the action and key details (GraphQL, returned fields, optional filter). No wasted words.

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 no output schema, the description partially covers return fields but omits pagination, limit defaults, and result count. The list operation's behavior is not fully described considering the 3 parameters and typical expectations for list endpoints.

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 100%, so the schema already documents all parameters. The description adds minimal value beyond restating the namespace filter option and product ID type.

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 'List all metafields attached to a product via GraphQL.' It specifies the resource (metafields) and verb (list), and distinguishes from siblings like get_product_metafield and list_metafield_definitions by focusing on product metafields.

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 implies use for listing product metafields but does not explicitly state when to use this vs alternatives (e.g., get_product_metafield for a single metafield) or provide exclusion criteria.

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