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

Annotations already declare readOnly, idempotent, openWorld=false and non-destructive, so safety is covered. The description goes beyond them by disclosing the actual return shape — two command variants, one with full registry URLs and a shorter @ndeko form gated on components.json declaring the namespace — which matters because no output schema exists.

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 tight sentences, front-loaded with the action and artifact, followed by the return-value nuance. No filler and nothing that repeats the schema verbatim.

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 two-parameter tool with no output schema, the description covers purpose, the package-manager dimension, and the two return forms. It stops short of stating whether names are validated against the registry or how invalid input surfaces, which would be the last piece an agent needs.

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 coverage is reported at 0%, so the description must carry weight, and it partly does: it enumerates npm, pnpm, yarn and bun for packageManager and clarifies 'one or more' items for the names array. It adds no mapping detail beyond that — no mention of the npm default, the 30-item cap, or what happens with an unknown item name.

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 artifact: 'Build the shadcn CLI command that installs one or more ndekoui items'. This is unmistakably distinct from siblings like get_item (fetch one item) and list_items (enumerate), and the agent knows the output is a command string, not data.

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?

Usage is implied by the purpose — call it when you need an install command — but there is no explicit when-to-use framing or routing versus get_item/list_items. The only conditional guidance given ('works in any shadcn project' vs 'the shorter @ndeko form for projects whose components.json declares the namespace') describes which output form applies, not when to pick this tool.

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