audit_group_keyboard

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

No annotations are provided, so the description carries full responsibility for behavioral disclosure. It only states the tool audits a rule group but does not mention side effects, authentication needs, rate limits, or whether it is read-only. The lack of such information reduces transparency.

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 a single sentence that is front-loaded with the core purpose and immediately follows with the key input requirements. Every word adds value, with no redundancy or filler.

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?

Despite having 4 parameters and an output schema, the description omits details about the level parameter, expected return values, and any prerequisites. For a tool with many siblings and no annotations, this brevity leaves the agent underinformed for correct invocation.

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 url, html, and session_id parameters by indicating they are mutually exclusive input sources. However, it does not explain the 'level' parameter (which has a default of AA) or provide constraints like format or length. With 0% schema coverage, more detail was needed.

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 audits the 'keyboard' rule group and specifies it covers 9 axe rules. It also lists the required input parameters (url, html, or session_id), making the purpose unambiguous.

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 says to provide one of url, html, or session_id, which gives basic usage guidance. However, it does not explain when to use this tool versus other sibling audit group tools (e.g., audit_group_aria, audit_group_color), nor does it mention any scenarios where this tool is preferred or not.

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