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

With no annotations, the description carries the burden of disclosing behavior. It details what the returned 'build kit' includes, notes conditional extra data for 'deep-decoded products', and explains resolution precedence. It does not mention auth or rate limits, but for a read-oriented aggregate tool, the disclosure is substantial.

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 three sentences, front-loaded with the main purpose and then elaborating on contents and use case. Every sentence adds value, though the detail is somewhat dense. It is efficient for a tool with high complexity.

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 lack of output schema, the description provides a strong overview of the return payload (design system formats, sections with specs and image URLs, user flows). It covers the main use case and special token data. Minor gaps remain: no explicit mention of error behavior or limits, but the description is largely sufficient for an agent to invoke the tool correctly.

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 schema has 0% description coverage, leaving the sole parameter 'site' completely unexplained. The description implies that 'site' refers to a product identifier ('clone/build like <product>') and mentions BYODS resolution, but it never explicitly states the expected format (URL, name, ID) or how to reference a product. The agent must infer meaning from context, which is insufficient.

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 clearly states the tool's function: 'Pull an entire product as an agent-ready build kit' with a specific verb and resource. It also enumerates the included components (design system, pages, sections, flows), which distinguishes it from sibling tools like get_design_system or get_section.

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 provides explicit usage context: 'Call this once for "clone/build like <product>" instead of many small calls.' It also mentions resolution order ('Your private BYODS systems resolve first'). It does not explicitly list exclusion cases, but the guidance is clear enough for most scenarios.

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