audit_group_time_and_media

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

No annotations are provided, so the description must fully disclose behavioral traits. It only states that the tool 'audits' the rule group, but does not mention if it is read-only, what side effects occur, or how results are reported. The description lacks transparency about error handling, concurrency, or resource usage.

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: two sentences covering purpose and input requirements. No superfluous text, and the information is front-loaded. However, it could be slightly restructured to list parameters more explicitly. Overall, it is efficient but minimal.

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 tool's complexity (4 parameters, no required, with output schema) and the presence of many sibling tools, the description is too sparse. It fails to explain what the audit produces, how to interpret results, or what happens if multiple inputs are provided. While the output schema exists, the description should still contextualize the tool's purpose within the broader suite.

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 input schema has 4 parameters (url, html, level, session_id) with no descriptions (0% coverage). The description adds context that these are exclusive options ('Provide one of: url, html, or session_id'), but does not explain the 'level' parameter (default 'AA') or clarify the format of 'html' content. The added value is moderate, partially compensating for schema gaps.

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 'time-and-media' rule group, specifically noting it covers 5 axe rules and requires one of three inputs (url, html, session_id). This clearly distinguishes it from sibling tools that focus on other rule groups (e.g., audit_group_aria, audit_group_forms).

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 the user must provide one of url, html, or session_id, which gives some usage guidance. However, it does not explain when to use this tool versus other group-specific tools, nor does it mention any prerequisites or exclusions. The sibling list shows many overlapping audit tools, so explicit guidance would be beneficial.

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