list_axe_rules

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

The description notes that each rule is exposed as its own tool, hinting at the return content, but does not explicitly state that this is a read-only operation or describe side effects. No annotations are provided to compensate.

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 two sentences: first states purpose, second explains the parameter. No redundancy, and it is front-loaded with the core action.

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 covers the main purpose and parameter, and since an output schema exists, the lack of return value details is acceptable. It could mention that this is a list operation, but overall it is adequate.

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 description adds meaning to the wcag_only parameter beyond the schema by explaining it filters rules tagged with WCAG conformance levels. This compensates for the 0% schema description coverage.

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 lists axe-core rules and distinguishes itself from siblings like list_wcag_rules by specifying 'axe-core rules'. The verb 'List' and resource are explicit.

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 implies the tool can be used to discover available rules before invoking individual rule tools, but it does not explicitly state when to use this tool vs alternatives like list_wcag_rules or list_automated_checks.

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