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

With no annotations at all, the description carries the full disclosure burden and doesn't meet it. It doesn't say whether the spec is pre-computed or generated on demand (which would imply latency or side effects), whether the 'domain lock' makes the artifact immutable, what happens if product_slug is unknown, or roughly how large the returned payload is—and there is no output schema to compensate.

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 no filler. It is dense with internal terminology, but no sentence is wasted.

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 four-parameter retrieval tool with no annotations and no output schema, the description covers what is fetched but not how the call behaves or what comes back. Naming the three bundled artifacts is genuinely useful, but the agent still has to guess at side effects and failure modes.

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 all four parameters are already documented in structured form and the baseline is 3. The description adds no parameter guidance—it never mentions corpus, the jewelry/audio variant enum, or how product_slug interacts with the productSlug alias, leaving the duplicate slug fields ambiguous.

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 verb 'Retrieves' and the named artifacts (redesign spec, theme token pack, domain lock) make the general shape clear, but the language is heavy internal jargon—'autonomous vertical redesign specification' and 'pre-generation domain lock' are not self-explanatory to an outside agent. It also does nothing to distinguish itself from siblings such as run_ux_radar_proof or standalone_page_draft_paid, which an agent could plausibly confuse with it.

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 offers no when-to-use condition, no prerequisites, and no alternative named. An agent has no signal for whether this is a first step before a redesign flow or a lookup of an existing artifact, which matters because the artifact names imply generation.

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