Accessibility Report Generate

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

With no annotations, the description carries the full burden and falls short: it does not disclose that the tool fetches/scans the given URLs, that it writes a report artifact to disk (implicit in the output_dir/output schema), whether it requires network access, or how failures are handled. Only the generic word "Generate" hints at a mutation.

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 short sentence is front-loaded and waste-free, but its brevity is under-specification rather than genuine conciseness. There is little structure to organize the missing detail.

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?

An output schema exists, so return values need not be explained here, but for a mutation tool with zero annotations and 0% parameter coverage the description leaves too much unspecified (what gets scanned, where output lands, what level controls). It is not adequate for the tool's complexity.

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 description coverage is 0% for three parameters, so the description must compensate and does not. It says nothing about the URL list, the meaning of the "level" enum-like default ("AA" WCAG conformance), or the output_dir destination.

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?

States a specific verb+resource ("Generate ... accessibility report"), so an agent knows the operation. However, it does not distinguish itself from the closely related siblings accessibility_axe_scan, accessibility_wcag_check, accessibility_color_contrast, and accessibility_aria_validate. The word "comprehensive" weakly hints at aggregation but never says so.

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?

There is no when-to-use guidance, no conditions, and no mention of the alternative scan/check tools. An agent receiving this alongside four narrower accessibility siblings has no stated rule for choosing this report generator over them.

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