Audit Shopify Catalog Health

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, so the safety profile is covered. The description adds scope details such as 'recent products' and 'across selected stores', but it does not disclose the return format, what exactly 'recent' means, or how results are presented. No contradiction with annotations.

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 a single, well-structured, front-loaded sentence that conveys all key functionality with no filler. Every clause contributes meaningful information about what the audit covers.

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?

Input schema and annotations cover parameters and safety, making basic invocation straightforward. However, there is no output schema and the description does not explain what the audit returns, whether results are per-store or combined, or how 'missing' fields are reported. This is a noticeable gap for a multi-dimensional audit tool.

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%, with the schema already documenting 'stores' and 'first' clearly. The description's mention of 'recent products across selected stores' loosely maps to these parameters but adds no additional semantic value beyond the schema.

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 names a specific action ('Audit') and resource ('recent products across selected stores'), then enumerates the exact checks performed: missing vendor, product type, SEO fields, featured media, media alt text, and active products without inventory. However, it does not explicitly differentiate itself from similar sibling tools like shopify_catalog_gap_report or shopify_compare_catalog, so it stops short of a 5.

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 intended use case is implied through the audit language and the listed data-quality dimensions, but there is no explicit guidance about when to choose this tool versus sibling audit/report tools. No alternative tools or exclusion criteria are mentioned.

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