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

Annotations already declare readOnlyHint, idempotentHint and non-destructive, so the safety profile is covered; the description adds real context beyond that: it explicitly 'changes nothing', refuses sites the user does not hold, and notes that the returned settings link to where each can be changed. Only the access/permission mechanics behind the refusal are left vague.

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 entire description is one sprawling run-on sentence that mixes the tool's purpose, eligibility rules, a field-by-field catalogue, and cross-references. The critical eligibility constraint and the read-only guarantee are buried mid-stream rather than front-loaded, and the archaic phrasing slows parsing.

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 must explain what comes back, and it does catalogue every returned setting including the nested structure of 'excluded' and 'search_rules'. That makes it functionally complete for an agent planning the call, even if the prose is hard to extract from.

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 parameter is already documented as 'A domain from list_sites.' The description's 'Name the site by its domain' restates the same information without adding format or validation detail, so the schema carries the burden entirely.

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?

Despite the indirect phrasing ('How a site of the user's own is set up'), the description makes clear this returns a site's configuration, enumerating the specific settings returned (tag, tag_docs, time zone, group, public, email_reports, excluded, search_rules). It distinguishes itself from siblings by ruling out public-stats sites and pointing to check_install and list_sites, though the core verb is never stated plainly.

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 gives one useful eligibility rule (a site read only because its stats are public is refused, since settings belong to its holders) and routes the agent to check_install once the tag is installed. But it never says when to prefer this over get_site_summary, get_overview, or other per-site reads, so the usage boundary is only implied.

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