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

Annotations already cover the safety profile (readOnly, idempotent, non-destructive, closed-world), and the description adds real operational context the annotations cannot: the default slim theme keeps responses compact, and the live_url null case is called out with the recommended agent behavior ('say so and offer publish rather than handing over a link'). That last point is exactly the kind of branch-handling guidance descriptions should carry; it stops just short of covering pagination/size limits on the pages array.

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?

Front-loaded with the payload summary, then exclusions, then defaults and optional flags — a sensible order for an agent scanning top-down. It is long and the 'brief'/'data_files' glosses duplicate the schema's own parameter descriptions, so a few phrases fail to earn their 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?

No output schema exists, so the description carries the return-shape burden and does so thoroughly: per-page fields, site-wide search settings, theme default vs full, and the specific null case for live_url. An agent has enough to call it correctly and to interpret the result without a second lookup.

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 description coverage is 67%, and the description compensates by framing `include` as the way to get more in one call and by giving the default and the round-trip rationale for include_theme_config. It repeats some of the schema's enum explanations rather than adding new detail there, which keeps it below a 5.

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?

Opens with a specific verb+resource ('Fetch details of a single site') and then enumerates exactly what comes back — pages, theme summary, search settings, publish status, URLs. It explicitly contrasts with get_page and get_site_changes, so an agent can place it precisely among siblings.

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?

Names the alternatives and the conditions that select them: get_page with view: 'structure' for the node tree, get_site_changes with include_versions: true for history, include for extra bundles, include_theme_config only when round-tripping the theme. Exclusion guidance is explicit rather than implied.

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