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

Annotations already declare read-only, idempotent, non-destructive and open-world, so the safety profile is covered. The description still adds real behavior beyond that: it fetches under a named agent identity, obeys robots.txt, performs deterministic (not LLM-judged) checks, and degrades gracefully by reporting when a page cannot be fetched.

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?

Three tight sentences: what it fetches, what it returns, and the reliability caveat. The payload (the audit output) is front-loaded and no sentence is filler.

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 does the work of enumerating returned findings (title, description, headings, structured data, canonical, language, links) and noting each carries a rationale and a fix. That is effectively complete for invocation; minor gaps remain on limits (page size, timeouts) and whether JS-rendered content is covered.

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 coverage is 100% and there is only one parameter, so the schema already carries the syntax with a concrete example URL. The description contributes only the qualifier 'public' page, which mildly constrains acceptable values but adds little beyond the schema. Baseline 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?

States a specific verb and resource ('Fetch one public web page as CitedBot') plus the exact deliverable ('what is wrong with it for AI answers and search'), with the 'one page' scope setting it apart from bulk-oriented siblings. It stops short of naming backlinks / check_llms_txt / check_ai_crawler_access, so the boundary is implied rather than explicit.

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?

Usage is implied — you call it to audit a single page — and the 'deterministic checks only' line sets a useful expectation about what kinds of findings come back. There is no explicit when-to-use/when-not framing, no prerequisite (e.g. page must be publicly reachable) and no routing to sibling tools for crawler access or llms.txt.

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