audit_ui_design_aesthetic

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

No annotations exist, so the description carries the full burden. It discloses that the tool rejects specific anti-patterns and returns polish steps, but does not mention whether the operation is read-only, any side effects, input constraints, or performance implications. 'Audits' implies read-only, yet deeper behavioral context is missing.

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 single sentence that front-loads the verb and resource, then lists specific anti-patterns and the output type. It is efficient, information-dense, and contains no filler words.

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 one parameter and no output schema, the description and schema together give an agent enough to call it correctly. It explains the input, the checks performed, and the output type. It could optionally reference sibling tools for performance or security to fully prevent mis-selection, but this is not critical for a simple audit tool.

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 schema already describes the code_snippet parameter as 'The HTML/CSS/React code to audit for visual aesthetic and usability', covering 100% of the parameter meaning. The description adds no extra detail about the parameter's format, scope, or limitations beyond what the schema provides.

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 states the tool audits HTML/CSS code, specifies concrete anti-patterns (plain browser defaults, raw unadjusted colors, missing active/focus states, poor contrast), and declares the output as 'exact polish steps'. This distinguishes it from sibling audit tools that target performance, security, or SEO, making the purpose unambiguous.

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 makes obvious that this tool is for UI design auditing of code snippets, giving an agent enough context to select it over other audit tools. However, it does not explicitly mention when not to use it or point to alternatives for performance or security audits, so it falls short of a 5.

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