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

Annotations already cover the safety profile (readOnlyHint=true, openWorldHint=false). The description adds genuinely useful behavior beyond that: deep-decoded products carry extra token data, and private BYODS systems resolve first. However, it omits response size/pagination behavior for what is clearly a large aggregate payload.

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 payload contents are front-loaded, which is good, but the prose leans on proprietary jargon ('agent-ready', 'deep-decoded', 'BYODS') that spends words without adding precision. It is dense and mid-length rather than tight.

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?

No output schema exists, so the description must carry the return-value burden — and it does describe the returned assets reasonably well. But it leaves the single input underspecified and says nothing about payload size, limits, or pagination for an aggregate 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?

There is one required parameter, 'site', at 0% schema description coverage, and the description never explains it — no format (URL vs. slug vs. product name), no resolution semantics despite mentioning BYODS resolution. The sole input is left fully 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?

States a specific verb (pull) and resource (product) and enumerates the exact payload: multi-format design system, pages, sections grouped by type, and user flows. It's clearly a bundle in contrast to the granular siblings, but it never explicitly names those siblings (get_design_system, get_screen_sections, get_user_flow) to help an agent choose between them.

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?

"Call this once for 'clone/build like <product>' instead of many small calls" gives an explicit use condition and names the alternative pattern (many small calls). It's clear context without explicit exclusions, so it stops short of a 5.

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