Get the short WunderUI rules

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

No annotations are provided, so the description carries the disclosure burden. It does communicate that this is a short, curated text payload meant to be pasted into an agent config file, which tells the agent what it will get back and how to use it. It stops short of stating the exact return format (markdown vs plain text) or length, but for a zero-parameter read this is largely covered.

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, no filler, with the core purpose and the ordering instruction front-loaded before the alternative. Every clause (content areas, CLAUDE.md destination, sibling pointer) carries 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 zero-param, read-only retrieval tool with no output schema, the description covers what the content is and when to call it. The only gap is not characterizing the response format or size, which would help an agent decide whether to load it into context.

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?

The tool takes no parameters, so the baseline is 4; there is nothing for the description to disambiguate. It correctly implies no arguments are needed by framing the call as a simple 'read this first'.

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 resource (short, always-on WunderUI rules) and enumerates its content scope (components, tokens, motion, copy), plus names the intended destination file (CLAUDE.md / AGENTS.md). This makes it instantly distinguishable from get_design_md, which it explicitly identifies as the fuller version.

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?

Explicitly says 'Read this first' and names the alternative and the condition that selects it ('use get_design_md for the full context'). Ordering guidance plus the sibling routing is exactly what an agent needs.

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