Get design inspiration from famous apps

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

With no annotations, the description carries the full burden of behavioral transparency. It discloses the IP caution (never copy logos/trademarks), the scope of content (palette directions and public UI patterns), and that it should be used to derive design tokens and confirm with the user.

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?

The description is information-dense and well-structured: main purpose, use cases, IP warning, and filtering options. No filler; the category list and caution are necessary.

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 tool with no output schema, the description covers the tool's content, use cases, safety constraints, and filtering. It doesn't specify exact return shape or pagination, but it implies a list of inspirations via 'pick an inspiration', which is adequate given the tool's scope.

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 covers only 33% of parameters, so the description compensates by explaining query as matching name/traits and listing all category values. It does not explain limit, but the default/max are in the schema, and limit is unambiguous.

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?

The description clearly identifies the tool as a library of design languages from ~100 famous apps, with explicit use cases for answering 'make it look like X' or building custom themes. It distinguishes itself from gallery presets by offering broader design directions.

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 description explicitly tells the agent to use it when offering broader design directions than gallery presets, answering 'make it look like X', or building a custom theme. It does not name a specific sibling tool for exclusion, but the contrast with gallery presets provides clear context.

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