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

Annotations already cover readOnly/idempotent/destructive/openWorld, so the description adds real value by disclosing that the preview URL is authenticated and that 'no public access token is issued' – an auth/access nuance not in the annotations. It does not describe rate limits or failure modes, keeping it at 4.

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 tight sentences with the read scope front-loaded and the auth caveat following. No filler, though the first sentence largely restates the title verbatim.

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 read-only, single-param tool with full annotation coverage, the description conveys what is returned (draft, revisions, preview URL) and the key access caveat. With no output schema present, it does enough, though a note on the return shape would push it higher.

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?

There is a single 'company' UUID parameter with 100% schema description coverage, so the schema fully documents it. The description adds no parameter-level detail, which is the expected baseline 3 under high coverage.

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) and concrete resources (current draft, article revisions, authenticated preview URL), and the 'before publishing' framing distinguishes it from the plain get/history siblings. It stops short of explicitly naming which sibling to use instead, so it lands at 4 rather than 5.

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?

'before publishing' implies the usage context, and 'No public access token is issued' hints at the pre-publish verification workflow. However, there is no explicit when-not or named alternative among the many summer_guides_* read tools, leaving the agent to infer the boundary.

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