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

The description adds useful behavioral context beyond annotations: the preview is private, uses MyReach's storefront renderer, and reflects the exact draft revision. However, it does not explain why readOnlyHint is false for a 'get' operation, what access/permissions are required for a private preview, or whether any preview state is created or persisted.

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 description is a single front-loaded sentence with zero filler. Every phrase earns its place, and nothing is repeated from the title or structured fields.

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?

The tool has an output schema, so return values need not be described. But with two parameters at 0% schema description coverage and a non-read-only annotation for a preview operation, the description leaves key details missing: what draftCapability does, whether the preview creates a session or expires, and why the operation is not read-only.

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%, so the description must compensate, but it never mentions draftId or draftCapability by name. 'Private preview' loosely hints that a capability may be required, but it gives no meaning, format, or usage guidance for either parameter.

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 and resource: get a private preview of the exact draft revision. It implicitly distinguishes a draft preview from get_page (published page) and from create/update tools, but it never names or explicitly contrasts any sibling tool.

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 guidance on when to use this instead of get_page, list_pages, or get_publication_status. The intended usage (preview a draft before publishing) is only implied; no when-not-to-use or alternatives are stated.

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