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

Annotations already declare read-only, idempotent, non-destructive, so safety is covered. The description adds the material behavioral fact that the tool returns a plan of steps rather than installing, that the theme write happens only once (tied to the themed flag), and that an icon-sprite copy step is conditionally included — real context beyond the annotations.

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?

Two sentences with the verb and resource front-loaded and no filler. The first sentence is a long triple-clause construction that takes some parsing, but every clause conveys a distinct step type rather than restating the title.

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?

There is no output schema, so the description must explain what comes back — it does, enumerating the returned steps and their conditional variants. It also covers the init prerequisite and the once-only theme write, leaving nothing essential an agent needs before calling it.

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%, including where style and tailwindCss values come from in components.json, so the schema already carries the parameter burden. The description reinforces the components.json/src-dir provenance and ties the theme step to the themed condition, but adds little that the schema does not already say, and never mentions the required name parameter.

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: 'Get the steps to install one Wisty UI item with the shadcn CLI,' and enumerates what those steps contain (npx command, theme step, icon sprite copy). It does not name or contrast any sibling such as get_component or get_example, so an agent must infer the boundary itself.

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?

There is no explicit when-to-use versus alternatives statement; the reader must infer that this comes after search_components/list_components. The description does give a concrete precondition chain (read components.json and check for src/ first; run shadcn init when there is no src/), which is useful but procedural rather than selection guidance.

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