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

Annotations already cover read-only, idempotent, non-destructive, closed-world, so the safety profile is settled. The description adds real context beyond them: what sections exist, that `style` changes which API variant is returned, and that `source` inflates the response with files an agent rarely wants.

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?

Front-loaded with the verb and the returned content, which is the right order for a read tool with no output schema. The long inline enumeration of sections partly duplicates the schema enum and the phrase "its examples by name" is slightly opaque, but nothing is filler.

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?

With no output schema, the description carries the burden of describing the return value, and it does so section by section, plus it explains the two optional parameters' trade-offs. Only the absence of sibling routing and of any size/token warning keeps it short of complete.

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 100%, so the parameters are already documented and the baseline is 3. The description adds marginal meaning — the "rarely need" steer away from `source` and the section-subset shortcut — but restates the `style` guidance the schema already gives.

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?

Uses a specific verb and resource ("Read one Wisty UI item") and then enumerates the payload it returns, so an agent knows exactly what comes back without an output schema. It never names or contrasts the sibling tools (search_components, list_components, get_example, get_install_command), so differentiation is only implicit.

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?

It offers useful in-tool guidance — narrowing via `sections` when the item is already known, and preferring the shadcn install command over `source: true`. However, it never states when to reach for this tool rather than search_components or list_components, leaving the sibling-routing decision to inference.

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