list_accessibility_articles

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

No annotations are provided, so the description must disclose behavioral details. It mentions 'get an overview', which hints at the output nature, but does not clarify whether the operation is read-only, paginated, or what exact fields (e.g., titles, links, content) are returned. This lacks sufficient behavioral transparency for an unannotated tool.

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 concise at two sentences. The first sentence is specific and actionable, while the second largely restates the scope but adds little new information. It is not overly verbose, though the second sentence could be considered somewhat redundant.

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 tool is simple, but the absence of an output schema places a burden on the description to explain the return value. The description offers a general idea of the content (overview of W3C WAI-ARIA patterns) but does not detail the response structure, such as whether it includes metadata, summaries, or links. This is adequate but leaves gaps.

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 only parameter, outputMode, is fully described in the schema with its enum values and default, so the schema already provides complete information. The description adds no extra parameter meaning, aligning with the baseline score of 3 for high schema 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's action ('List all available accessibility articles') and its resource ('e11y-mcp documentation repository'). It distinguishes itself from the sibling tools search_accessibility_articles and fetch_accessibility_article by emphasizing the comprehensive listing of all available content.

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 should be used when a complete overview of all accessibility articles is needed, given the word 'all'. However, it does not explicitly mention the alternative sibling tools or provide when-not-to-use guidance, so the usage context is only implied.

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