Analyze UI components to detect WCAG accessibility violations and get actionable fix recommendations. Improve compliance in React, Vue, or HTML files.
Analyzes UI components (React, Vue, HTML) for accessibility (a11y) compliance (WCAG) and provides actionable fix recommendations.
| Name | Required | Description | Default |
|---|---|---|---|
| file_path | Yes | Path to the UI component file. | |
| project_dir | No | Optional project directory context. |
Changes observed during successful MCP inspections.
v2.7.1Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already indicate readOnlyHint=true. The description adds context about the analysis scope (WCAG compliance) and output (fix recommendations), which enhances transparency without contradicting annotations.
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, concise sentence that conveys the tool's purpose without unnecessary words or repetition.
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?
The description is adequate for a simple analysis tool. It lacks details about the output format but given the straightforward purpose and no output schema, it provides sufficient context for an AI agent to decide to invoke it.
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 100% with descriptions for both parameters. The description does not add meaning beyond what the schema provides, so 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?
The description clearly states that the tool analyzes UI components for a11y compliance (WCAG) and provides fix recommendations. It names specific frameworks (React, Vue, HTML) and distinguishes itself from sibling tools like veto_lint_rules or veto_security_scan.
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?
No explicit guidance on when to use this tool versus alternatives is provided. The description implies its purpose but does not mention when to avoid using it or suggest sibling tools for other tasks.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.