validation.w3c.autofix_safe.v1

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

No annotations are provided, so the description carries the full burden of behavioral disclosure. The description mentions 'safe file autofix' which implies in-place modification of files, but it does not state whether this permanently mutates project files, what files are affected, whether the operation is reversible, or the nature/volume of validation output. For a tool that performs file autofix (a side-effecting operation), this is a significant transparency gap.

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 concise sentence with no wasted words, which is structurally sound. However, it fails to front-load any parameter or usage guidance, packing limited value into the sentence available. Given the tool's complexity (5 params, autofix with side effects), a single 13-word sentence under-specifies rather than demonstrating genuine efficiency.

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?

An output schema exists, so the description needn't explain return values, which helps. However, for a tool combining file autofix (a destructive/mutating operation) with W3C validation, the description omits critical context: which files get modified, whether paths restricts the scope, how level (error vs warning) affects the autofix threshold, and how baseline_pages/after_pages interplay. The 'safe' qualifier does some work but leaves too much to inference.

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 description coverage is 0%, so the description carries full burden for parameter meaning. The description 'Run safe file autofix and W3C before/after validation' implies the baseline_pages/after_pages parameters map to before/after states, and 'safe' implies max_files limits scope, but none of the 5 parameters (level, paths, max_files, after_pages, baseline_pages) are explicitly explained. With high parameter count and zero schema coverage, the description does not compensate.

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 states a clear verb+resource combination: 'Run safe file autofix and W3C before/after validation on raw HTML pages.' It distinguishes the tool from siblings by mentioning 'safe' autofix and 'raw HTML pages,' which differentiates it from w3c_validate_urls_raw (URL-based, no autofix), w3c_validate_pages (validation only), and w3c_validate_and_recheck. The purpose is clear, though it doesn't explicitly name sibling alternatives.

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?

No guidance is provided on when to use this tool versus alternatives. Given the sibling set includes w3c_validate_urls_raw, w3c_validate_pages, and w3c_validate_and_recheck, an agent would benefit enormously from knowing when autofix is appropriate versus when only validation or URL-based checking should be used. The description offers no context or exclusions.

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