validation.w3c.validate_urls_raw.v1

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

No annotations are provided, so the description carries full behavioral burden. It does not disclose that this is a network operation hitting an external service, potential rate limits, latency, side effects, or what happens on validation failure. 'Using fetched raw HTML' hints at the fetch mechanism but provides no details about network behavior or error handling.

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. It is appropriately brief, though it could benefit from one additional sentence about usage or parameters without hurting 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?

Despite having an output schema, the tool is a network-mutating external-service call with two undocumented parameters, zero annotation coverage, and a meaningful sibling cluster (validate_pages, validate_and_recheck, autofix_safe). The description does not clarify how this tool differs from validate_pages, what level thresholds mean, or how results are signaled. This is materially incomplete.

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 must compensate for both parameters. It mentions neither 'urls' nor 'level'. The 'level' parameter has an enum (error/warning) but no explanation of what each value means in context, and 'urls' semantics (format, count limits) are entirely unexplained.

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 specific verb+resource ('Validate live URLs through W3C Nu Validator using fetched raw HTML'). It clearly distinguishes from siblings like validate_pages (which likely validates rendered pages) by noting it uses 'fetched raw HTML', giving some differentiation among the w3c_* sibling cluster.

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 provides no when-to-use guidance, no exclusions, and no mention of alternatives. Among siblings like validate_pages and validate_and_recheck, there is no indication of when to choose raw HTML validation over page-based validation or when rechecking/autofix would be more appropriate.

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