Audit Real Browser UI

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

With no annotations, the description carries the burden and does well: it declares the operation read-only and bounds scope (no form submissions, no remote browsing). It doesn't say where results land or how report overwriting behaves, but the safety profile is clearly disclosed.

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?

A single dense sentence, front-loaded with the read-only audit framing before the defect list and exclusions. The defect enumeration is long but each item is informative, with minimal waste.

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 6-parameter tool with no output schema, the description covers operation, safety scope, and viewport behavior adequately; destination and overwrite details are delegated to the schema's reportPath/overwrite descriptions. Missing only explicit guidance on prerequisites (a running local server) and result format.

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 coverage is 83%, so the schema already documents url, overwrite, reportPath, projectRoot, and viewports well. The description only echoes 'at multiple viewports' and adds nothing about the URL/port constraint or timeout semantics beyond the schema, so baseline 3 applies.

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?

Specific verb+resource ('Read-only audit of localhost web UI') with an enumerated set of detected defects (overflow, offscreen elements, broken images, unlabeled controls, etc.). It clearly differs from siblings like review_ui, inspect_ui_project, and capture_ui_screenshots by being an automated defect-detection audit.

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?

It establishes the setting ('localhost web UI using project Playwright') and two exclusions ('no form actions or remote browsing'), which implies when it fits. However, it never names an alternative tool or states when to prefer review_ui or capture_ui_screenshots, so routing is left to inference.

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