Get a WunderUI agent skill

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

With no annotations, the description carries the safety/auth burden and does so partially: it discloses that Pro skills require a valid Pro key via WUNDERUI_LICENSE_KEY and that referenced scripts are not included. It does not say what happens on an unknown skill name or an invalid/missing key.

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 short sentences, front-loaded with the return value before the auth caveat and the scripts note. Slightly dense with parentheticals but every sentence contributes distinct information.

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 one-parameter read tool with no output schema, the description covers what is returned, the auth gate, and a key limitation. Only failure/error behavior for bad names or missing keys is left 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?

Schema coverage is 100% and the single required `name` parameter already carries examples (wunderui-theme, wunderui-screen). The description adds no further naming syntax or constraints, so baseline 3 applies.

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?

"Returns one skill's instructions (its SKILL.md)" gives a specific verb, resource, and source (wunderui.com), which is clear enough to pick apart from list_skills. It does not name the sibling explicitly, so an agent must infer that list_skills enumerates and get_skill fetches a single one.

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 phrase "so the agent can follow the workflow without installing the skill" states the situation that selects this tool over installing the skill. No explicit exclusions or alternative tool names are given, so it stops short of full when/when-not guidance.

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