listMetaobjects

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

No annotations provided, so the description must fully disclose behavior. It reveals the case-sensitivity requirement and empty-result behavior, but lacks details on pagination (cursor, limit) and potential performance 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?

Two sentences, no fluff, gets straight to the point. Each sentence adds necessary context without redundancy.

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 tool with 3 parameters, no output schema, and no annotations, the description covers the required parameter well and suggests a prerequisite step. However, missing pagination guidance leaves a small completeness gap.

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 33% (only 'type' has a description). The description adds meaning for 'type' (case-sensitive, discover through definitions), but does not explain 'limit' or 'cursor', which are important for pagination.

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 metaobjects of a given type' and specifies that the type must be a case-sensitive identifier like 'shopify--color-pattern'. This distinguishes it from sibling tools like listMetaobjectDefinitions, which serve a different purpose.

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?

Explicitly advises to run listMetaobjectDefinitions first to discover valid types, and clarifies that a non-existent type returns an empty result (not an error). This guides usage, though it does not mention when not to use the tool or compare with other list tools.

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