audit_group_name_role_value

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

With no annotations, the description carries the full burden. It mentions the tool audits 7 axe rules and requires one of three inputs, but does not disclose whether the tool is read-only, requires specific permissions, or has any side effects. This is adequate but not thorough for a black-box 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 very concise, with two sentences that front-load the action and then specify input requirements. No wasted words, though a slight expansion on the level parameter would not harm conciseness.

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?

Given the complexity (4 params, many siblings, output schema exists), the description provides the core purpose and input constraint. It lacks mention of the output format (though output schema is present) and does not differentiate from siblings enough. Adequate but could be more complete.

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 coverage is 0%, so the description must compensate. It clarifies that url, html, and session_id are mutually exclusive options, adding value. However, it omits the 'level' parameter, leaving its purpose undocumented. Partial compensation for missing schema descriptions.

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 it audits the 'name-role-value' rule group, which is a specific set of 7 axe rules. This verb+resource combination distinguishes it from sibling tools like audit_group_aria or audit_group_color.

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 specifies that one of url, html, or session_id must be provided, giving a clear usage condition. However, it does not guide when to use this tool instead of other audit_group_* siblings, which would be helpful given the large number of similar tools.

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