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

Annotations already declare readOnlyHint, idempotentHint and destructiveHint=false, so safety is covered by structured data. The description usefully adds the return format (markdown) and the breadth of content, but says nothing about response size, pagination, or how the 'all' topic affects payload.

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?

One sentence, front-loaded with the essential subject (what the payload is), followed by a scannable list and a short call to action. The enumeration is long but each item maps to a real section, so it earns its space.

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 correctly states the return format and content coverage; with annotations handling the safety profile and the schema handling the single parameter, nothing material is missing for an agent to call this correctly.

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% and the single enum is self-documenting with a default, so the baseline is 3. The description's section list loosely mirrors the enum values but adds no syntax or selection guidance beyond what the schema already states.

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?

A concrete verb+resource: it returns the Wingo UI design system as markdown, and the section list tells an agent exactly what content to expect. It does not, however, differentiate itself from the overlapping sibling get_theme_tokens, which likely covers the 'tokens' section it advertises.

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?

'Follow them for every screen you build' gives a clear, unconditional usage context, so the agent knows this is guidance to apply broadly. There is no guidance on when NOT to use it or how it relates to alternatives like get_theme_tokens and get_component, which is the main gap.

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