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

Annotations already declare readOnlyHint, openWorldHint, idempotentHint, and destructiveHint=false, so the safety profile is covered. The description adds valuable behavioral context beyond annotations: it performs live HTTP requests, runs ~3-5 seconds, and returns structured check results. No contradictions with annotations.

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 dense but front-loaded sentence: purpose first, then check list, then output, then latency. The list of 19 checks is long but valuable for disambiguation; no wasted filler words.

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 an output schema present, return values do not need full explanation. The description covers the tool's main inputs, its live HTTP behavior, expected duration, and output format. It does not mention error conditions or rate limits, but for a read-only audit tool with good annotations this is adequate.

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. It only implicitly indicates that 'url' is the site to scan; it does not specify URL format, required scheme, or constraints. This is minimal added meaning beyond the exists-as-required-string fact.

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 verb ('assess'), the resource ('how AI-callable a site is'), and the concrete output (level 0-5 plus per-check pass/fail with evidence and remediation pointers). The enumerated 19 checks distinguish it from siblings like run_site_audit or summarize_scan_for_humans.

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?

Explicitly starts with 'Use this when you need to assess how AI-callable a site is,' giving clear context for invocation. It does not mention exclusions or name alternative tools, but the context is specific enough for an agent to select it appropriately.

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