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

readOnlyHint=true already tells the agent this is a safe, non-mutating read, so the description's remaining job is to disclose the return shape, which it does at a high level (install command, CSS imports, provider). It adds the 'call once' hint, implying the guide is stable and need not be re-fetched, but says nothing about output format, size, or whether the guide is code or prose.

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 plus a compact parameter clause; the output contents are front-loaded before the usage rule and the parameter explanation. Dense and largely waste-free, though the trailing framework list is redundant with the enum it sits next to.

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 read-only, zero-required-param guide tool with no output schema, the description covers what is returned and when to call it. What remains unstated — the exact response shape and whether the guide is code vs. prose — is modest, and the annotation already carries the safety profile.

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 the enum values are already fully documented in the schema, making 3 the baseline. The description's inline list is actually narrower than the schema enum — it omits 'nuxt' and 'inertia-vue' and collapses inertia-vue into 'vue' — so it adds little and slightly under-represents the real options.

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 names the concrete payload it returns (install command, CSS imports, provider, app skeleton), which is far more specific than the title's 'how to install and set up'. It implicitly distinguishes itself from the component/token siblings (get_component, list_tokens, search_components) by being the scaffolding guide, though it never names 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?

The imperative 'Call once before building UI' gives explicit timing guidance that no sibling tool provides, telling the agent this is a prerequisite step rather than a lookup. It stops short of naming an alternative or a when-not-to-use condition, but the sequencing instruction is clear and actionable.

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