Accessibility Wcag Check

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

No annotations are provided, so the description carries the full behavioral burden. 'Check' weakly implies a read-only operation, but it discloses nothing about permissions required, whether results are cached, or what a compliance result contains, leaving a mutation/read ambiguity unresolved.

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 with no waste is structurally clean, but this brevity is largely under-specification rather than genuine conciseness, so it only meets the minimum viable bar.

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 described, but with zero annotations and zero parameter documentation the description leaves too much implicit for a compliance-check tool spanning three undocumented inputs.

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% and no parameter is enums, so the description must compensate, yet it explains none of entity_type, entity_id, or level. The level parameter's default of 'AA' (a WCAG conformance level) is a natural thing to document and is ignored.

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 ('check') and resource ('WCAG compliance') scoped to 'entity content'. This is clearer than the name alone, but it never distinguishes itself from the very similar accessibility_axe_scan, accessibility_color_contrast, or accessibility_aria_validate siblings.

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 prerequisites, and no mention of when a sibling such as accessibility_axe_scan or accessibility_report_generate would be a better choice. The agent must infer usage entirely from the name.

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