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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false, covering the safety profile. The description adds value by stating that the tool returns 'latest content JSON' and by flagging the need for an editToken on anonymous pages—details beyond the annotations.

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?

Two concise sentences with no filler. The core purpose is front-loaded ('Read a landing page draft...') and the additional condition about editToken is stated directly. Every sentence earns its 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?

Given the rich annotations (readOnly, idempotent, non-destructive) and the presence of an output schema, the description is largely complete for a read operation. It covers the key edge case (anonymous pages) and the return content. It could arguably mention that it retrieves drafts specifically, but the title already implies that.

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?

The schema has no parameter descriptions (coverage 0%). The description adds meaning for editToken ('For anonymous demo pages, include the editToken') but does not explain pageId, though its name is reasonably self-explanatory. It partially compensates for the schema gap but not fully.

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 states a specific verb ('Read') and a clear resource ('a landing page draft') and adds what is returned ('latest content JSON'). It distinguishes itself from sibling operations like page_create or page_publish by being explicitly a read operation, and the mention of 'anonymous demo pages' and 'editToken' further differentiates it.

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?

The description provides a clear condition for when to include the editToken ('For anonymous demo pages'), which is a usage guideline. However, it does not explicitly state when to prefer this tool over its read siblings like page_preview or when not to use it, though the read-only nature is implied.

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