Check published Ghost pages

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

Annotations already declare readOnlyHint, idempotentHint, openWorldHint, and destructiveHint=false, so safety is covered. The description adds genuine value beyond that: it discloses the external HTTP-checking behavior (open world), the URL source (Ghost or GHOST_PUBLIC_PAGE_URL_TEMPLATE), and that checks run 'once' (no retry loop). It omits rate limits and auth requirements, keeping it below a 5.

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 that leads with the verb and resource and packs the verification targets efficiently. No filler, though the constraint-heavy clause about URL templates makes it slightly dense.

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?

An output schema exists, so return values need not be explained, and annotations carry the safety profile. However, the undocumented required parameter and the absence of usage context leave meaningful gaps for an agent to call it 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 0% and the single 'pages' parameter is never described in the text. The reader cannot learn from the description what the array elements (id, updated_at) are for or why updated_at is required alongside id, so the description fails to compensate for the coverage gap.

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 (read/verify) and resource (current published pages) and enumerates the concrete checks performed: HTTP status, title, canonical URL, and SEO metadata. Its 'pages' scope is distinguishable from the sibling check_live_posts, though no sibling is named directly.

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 prerequisites, and no alternatives named (e.g., check_live_posts, get_page). The agent must infer that this is a post-publish verification step from the word 'verify' alone.

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