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

Annotations already declare readOnly, idempotent, openWorld and non-destructive, so the safety profile is covered. The description adds genuinely useful behavioral context beyond that: the scope is limited to public http/https sites and results come from a 24-hour cache shared with scan_website, which tells the agent why repeated calls may return identical data.

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 core scope is front-loaded in the opening clause, followed by an enumerated list of checked dimensions and a short cache note. It is dense but every clause carries information; the middle enumeration is slightly long but earns its place.

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 describing the return contents (crawler allow/block status, llms.txt presence, structured data types, title/description quality, and checks with fixes). Combined with annotations covering safety and cache behavior, an agent has enough to invoke it correctly, though it does not state error behavior for non-public or unreachable URLs.

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 url parameter has 100% schema description coverage including the public-sites constraint, so the schema already carries the semantics. The description adds nothing per-parameter but nothing is missing either; a 4 reflects a fully documented lone parameter.

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 uses a specific verb ('check') and a precise resource ('whether AI assistants and answer engines can read and quote a public website'), then enumerates the concrete dimensions inspected (robots.txt crawler allowances, llms.txt, structured data, title/description). This is far more than a restatement of the name and lets an agent distinguish it from sibling scan_website.

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 implies the tool is for auditing AI-crawler readability of a public URL and notes the shared 24-hour cache with scan_website, which hints at a relationship, but it never states explicitly when to pick this tool over scan_website, explain_check, or score_local_presence. Usage is left to inference.

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