atlas_ui_ux_designer

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It reveals key behaviors: scouring the internet for inspiration, generating code, providing multiple design options, including images, and offering accessibility guidance. This goes beyond a simple purpose statement, though it omits potential limitations or side effects.

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 a concise two sentences with the core purpose front-loaded. It efficiently lists key features without redundant filler, though words like 'Advanced' and 'best' add slight marketing tone without substantive value.

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?

Given the tool's complexity (7 parameters, no output schema, no annotations), the description provides a partial picture. It mentions outputs (images, code, accessibility guidance) but lacks details on the structure of the response, usage prerequisites, or example scenarios. The absence of an output schema makes this gap more significant.

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 input schema has 100% coverage with descriptions for all seven parameters, so the description does not need to explain them. The tool-level description adds context about design options and accessibility but not specific parameter semantics beyond the schema. Baseline 3 is appropriate.

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?

Description clearly states the tool is an 'Advanced UI/UX designer' that performs specific actions: finding design inspirations, generating production-ready code, providing multiple design options, and offering accessibility guidance. It distinguishes from sibling tools like atlas_css_wizard or atlas_animation_studio by focusing on the full UI/UX design process.

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 implicitly conveys that this tool is for UI/UX design tasks, but it does not explicitly state when to use it over alternatives or provide exclusions. There is no mention of when not to use it or how it compares to related tools such as atlas_css_wizard.

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