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

The annotations already declare readOnlyHint, idempotentHint, destructiveHint=false and openWorldHint=false, so the safety profile is fully covered without the description. The description does add value by disclosing what information comes back (including pending changes), which matters because there is no output schema, but the phrasing is metaphorical ('what it is on', 'waiting to be kept') rather than naming concrete fields.

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 front-loaded sentence with four parallel clauses and no filler. It is appropriately sized for a read-only status check, though the figurative wording of the last two clauses costs some precision.

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 two-parameter read-only tool with full schema coverage and complete annotations, the description is close to sufficient: it covers what the tool reports. It leaves unclear how the site/draft_id combination changes behavior and how this differs from the many sibling read tools, which an agent would need to know to select correctly.

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 100%, and the parameter descriptions themselves explain the optional site and the draft_id semantics (the id from create_preview, not the code in the link). The tool description adds nothing about parameters, so it sits at the baseline where the schema carries the load.

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 names a specific verb ('check') and resource (a site) and enumerates what the check reports: published state, last publish time, current contents, and pending unpublished changes. It stops short of distinguishing this from siblings such as history or list_pages, which an agent might reach for when asking about a site's state.

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?

There is no explicit when-to-use guidance, no exclusions, and no mention of any sibling tool. The only routing hint is implicit: the schema's draft_id parameter suggests this also answers questions about previews, but the description never says when to prefer this over history or read_page.

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