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

Annotations already cover the safety profile (readOnly, idempotent, openWorld, non-destructive), and the description adds real context beyond them: no account required, no model is invoked, and a semantic distinction between retrieval crawlers (which gate citation) and training crawlers (which cost nothing). It stops short of stating rate limits or latency characteristics, which is the only missing behavioral detail.

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?

Two sentences, front-loaded with the free/no-account hook and the core value proposition, with the analyze_site routing at the end where it is most useful. The second sentence is dense and comma-chained, packing five return-value items into one clause, which slightly hurts scannability.

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 single-parameter read tool with annotations and an output schema, nothing an agent needs to call it correctly is absent — auth requirements, model behavior, return categories, and the sibling boundary are all covered. The output schema carries the return shape, so the summary list in the description is a bonus rather than a gap-filler.

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 a single required url parameter already documented with a format example, so the schema does the heavy lifting. The description adds no extra syntax, normalization, or domain-handling detail beyond what the schema provides — the baseline 3 applies.

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 — read a website the way an AI engine does — and immediately scopes the output (crawler access split between retrieval and training, identity files, Organization schema, score out of 100, fixes). It also explicitly distinguishes itself from the sibling analyze_site, so the agent can pick between them without opening either schema.

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?

Gives an explicit when-to-use (before an engine answers about the site) and an explicit when-to-use-the-other ("for whether the engines actually name the site, run analyze_site"). It also removes cost/prerequisite friction up front with "Free and instant, no account."

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