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

Annotations already declare readOnly/idempotent/non-destructive, so the redundant 'Read-only' adds little. The description does add genuine behavioral context beyond the annotations: the account-token authentication requirement and the full scope of what the read surfaces (deploy history, restore availability, domain renewal state).

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?

A single sentence with the prerequisite front-loaded and the returned fields grouped as a scannable list. It is slightly run-on but every listed item corresponds to a distinct aspect of the read, so little is wasted.

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 compensates by enumerating the return content (liveness, links, deploys, restorability, domains, email), and annotations cover the safety profile. It is close to complete for a one-parameter read tool; only pagination/response-shape detail is absent.

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 the single 'site' parameter is fully documented in the schema with an example address. The description adds no syntax or format detail beyond that, so 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 ('One read of a site') and enumerates what the read covers: live status, links, deploys, restorability, domains, email. This clearly separates it from list_sites (plural) and check_live (single concern), though it never names a sibling to reinforce the distinction.

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 by 'One read of a site' versus the list-oriented siblings, and the '(needs account token)' prerequisite is stated. However, there is no explicit when-to-use vs when-not guidance and no pointer to the alternative tools for the same data.

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