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

With no annotations, the description carries the full burden and does well: it discloses that it reads only shopper-visible pages, requires no login or app install, and returns fixes in priority order. It never states the read-only nature as a formal guarantee or mentions latency/rate limits, leaving a small gap.

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 core action is front-loaded in the first clause, and each subsequent element (use-case questions, no-login constraint, prioritized output) earns its place. The three quoted questions are slightly verbose and could be compressed, keeping it out of 5 territory.

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 single-parameter read-only audit with no annotations and no output schema, the description covers purpose, behavioral constraints, and the shape of the result (score out of 100, prioritized fixes). A little more on the returned report structure would make it complete.

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?

There is a single parameter with 100% schema description coverage, so the schema already documents the domain format and examples. The description adds no syntax or format detail beyond what the schema provides, making the baseline 3 correct.

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?

States a specific verb (audit) and resource (a real Shopify store), plus the scope (public pages) and the four scored dimensions (speed, SEO, trust, product pages). This is unmistakably distinct from the financial-calculation siblings, so an agent can route to it without opening any schema.

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?

Names the concrete questions the tool answers ("why is my store not converting?", "how fast is my store?", "what should I fix first?"), which gives clear context for when to invoke it. It stops short of explicit exclusions or naming an alternative sibling, so it stops at 4 rather than 5.

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