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

No annotations are supplied, so the description carries the full burden. It does disclose the return payload in useful detail (color roles with area ratios, type scale, polarity, anti-patterns), which is real value for an output-schemaless tool, and "Extract ... from real products" implies a read. But it says nothing about what happens for an unknown/uncatalogued slug, latency, quota, or whether results are cached or live-computed.

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?

A single front-loaded sentence with the verb and output first, followed by a dense parenthetical inventory and the "ready for Tailwind or styles.css" payoff. Nothing is redundant, though the long parenthetical is heavy for one sentence.

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 two-parameter read tool with no output schema, enumerating the returned fields is the right compensation and largely works. However, with zero annotations and no discussion of the no-argument list mode or failure behavior, an agent still has gaps on edge cases.

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 both parameters are already documented including the list-all fallback, giving a baseline of 3. The description adds no meaning about styleSlug versus productSlugOrDomain, their interaction, or precedence when both are supplied.

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 and resource: "Extract computed hero Design DNA and CSS variable specifications from real high-growth products," then enumerates the concrete artifacts (5-color roles, font families, radius scale, theme polarity, hero layout, anti-patterns). It is clear what comes out, but it never names or contrasts with siblings like earlylore_inspect_product, which also targets a single product and is the most likely confusion point.

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?

Usage is only implied: pull a reference product's design tokens for Tailwind/styles.css. There is no explicit when-to-use versus earlylore_inspect_product or earlylore_compare_products, and no when-not guidance. The mode-selection hint (omit both slugs to list all style overviews) lives only in the schema, not the description.

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