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

The description adds meaningful behavioral context beyond the readOnly/openWorld/destructive annotations: it reveals the tool makes an external fetch, details the scan categories, and explicitly cautions that a clean result is not a full content-safety guarantee. This is precisely the kind of transparency agents need for a web-scanning 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 dense but every clause earns its place: it defines the threat categories, gives the invocation trigger, and sets expectations for the result. The structure front-loads the core action before the caveat.

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?

For a one-parameter, read-only, no-output-schema tool the description is largely complete: it covers what is scanned, when to call it, and how to interpret a clean result. It does not specify the exact return shape (e.g., boolean vs. list of findings), but the interpretation caveat compensates for most of that gap.

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 single parameter is fully documented in the schema (URL, required, format described). The description adds no new parameter-level semantics, but with 100% schema coverage the baseline of 3 is appropriate.

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 fetches a URL and scans for agent-hijacking content, then enumerates specific pattern categories. The purpose is concrete and distinct from the general site-audit sibling tool.

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?

It gives an explicit trigger condition: 'Call this before an autonomous browsing or checkout flow acts on instructions found on a page.' It lacks an explicit when-not-to-use or comparison to site-audit__audit_site_accessibility_and_agent_safety, so it stops short of a full 5.

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