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

Annotations already mark this as readOnly and openWorld, and the description adds rich behavioral context: it scans a public sitemap, checks specific criteria (≥180 days, season mismatches, retail-calendar windows), and returns work orders with estimated credit costs. This goes well beyond the annotations and provides clear expectations about what the tool does and produces. No contradiction exists.

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 exactly two sentences: the first states the core purpose and a key constraint (no account needed), the second details the scan criteria and return value. Every clause adds value, and the most important information is front-loaded. There is no wasted text.

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's single required parameter and the presence of an output schema, the description is fully complete. It explains what the tool does, how it works (sitemap scan), what it detects, and what it returns (work orders with pre-filled fixes and credit costs). It also orients the user in the broader toolset by linking to create_tryon_job.

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?

The input schema has 100% coverage with a well-described 'store_url' parameter (domain/URL with example). The description does not add additional parameter semantics, so the baseline score of 3 is appropriate—the schema fully handles parameter documentation.

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 opens with a specific verb and resource ('Audit a Shopify store's listing photos'), clearly distinguishing it from sibling create/get tools. It further elaborates with concrete audit dimensions (stale photos, season mismatches, retail-calendar windows), leaving no ambiguity about the tool's function.

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 states 'no account needed' and 'Scans the public product sitemap,' implying this is for public store audits without authentication. It also references 'pre-filled create_tryon_job fixes,' showing a clear workflow connection to that sibling tool. However, it stops short of explicitly saying when not to use this tool or naming alternatives, so it earns a 4 rather than a 5.

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