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

Annotations already cover read-only/non-open-world safety, and the description adds genuinely new operational context: Pro items require a valid Pro token, and the standalone shape yields a self-contained .tsx depending only on react and motion. It stops short of describing error behavior or what happens when a Pro item is requested without a token.

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?

Three sentences, purpose front-loaded, alternative routing second, parameter behavior last. Dense but readable; the parenthetical "(free components)" and the trailing shape clause are slightly compressed rather than cleanly structured.

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 carries the return-format burden and does so for both shapes (files with install paths vs. one inlined .tsx). Only the Pro-token failure mode and the exact file payload contents remain unstated.

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?

With 100% schema coverage the baseline is 3, but the description adds meaning beyond the schema text: standalone is scoped to free components and explicitly requires no Tailwind and no other items, which constrains expectations more than the schema's "styles and helpers inlined" wording.

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 first sentence states a specific verb and resource (raw files of one item, with install paths) plus the audience constraint that defines the tool (projects that cannot run the shadcn CLI). It is clearly distinguishable from get_install_command and get_item.

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?

"Prefer get_install_command" explicitly routes the agent to the alternative and the preceding clause gives the condition that selects this tool instead. The one gap is that it does not say what to do if a Pro token is unavailable (error vs. partial result).

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