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

Goes well beyond the annotations' safety profile: no JavaScript execution, results limited to the first HTML response and Set-Cookie headers only, no consent cookie sent, address and caller IP not stored, and an explicit rate limit of a few scans per 10 minutes. It also disclaims legal qualification, which guards against over-interpreting results.

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?

Four tight sentences, each carrying distinct load: scope, method limits, output contents, privacy, rate limit. The core operation is front-loaded in the first clause; nothing is padding.

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?

With no output schema, the description still tells the agent what comes back (tracker list with provider slugs where the catalog maps to a fiche, plus a link to the scanner page). Privacy, rate limit, and the legal caveat round out what an agent needs to call and interpret this correctly.

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 100% and there is a single parameter, so the schema already documents the URL format (http/https, ports 80/443, no username). The description restates 'public URL' and the no-consent condition without adding parameter-level syntax or format detail beyond the schema, matching the baseline 3.

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?

States a specific verb (fetch/report) and resource (one public URL's HTML response and Set-Cookie headers) with the precise scope: single fetch, no consent cookie, no JS execution. This is clearly a one-off site scan, readily distinguishable from catalog lookups like get_provider/list_providers.

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 'before consent' framing implies the use case and the rate limit signals it is not for bulk work, but the description never explicitly says when to choose this over the sibling provider-catalog tools or when not to scan. Usage is inferable rather than stated.

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