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

Annotations already declare readOnlyHint=true, destructiveHint=false and openWorldHint=false, so safety is covered. The description adds real value beyond that: 'A screenshot never publishes' and 'Isolated layout only' confirm the operation has no side effects on live content. It stops short of explaining version-mismatch failure behavior implied by expectedVersion.

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?

Three short sentences, front-loaded with the core action and followed by the required-param note and the key scoping constraint. No filler or repetition; every sentence carries a distinct fact.

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?

There is no output schema, and the description does not describe the returned image artifact (dimensions, format specifics, or how it is delivered). It also omits the required controlToken entirely, so an agent cannot fully construct a call from the description plus schema alone. Adequate for the main purpose but with clear gaps.

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 carry the burden, but it only mentions two of three required parameters ('Requires draftID and expectedVersion') and never explains controlToken, a required 20-200 char parameter that is presumably an auth/authorization token. No format, semantics, or conflict behavior is given for expectedVersion either.

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?

States a specific verb and resource ('Renders an exact private draft version as an MCP PNG'), which distinguishes it from read_draft, render, and get_canvas. The phrase 'MCP PNG' is slightly jargon-heavy but the scope ('private draft version', 'isolated layout only — not the live TV') makes the target unambiguous.

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?

Gives clear context ('for the Preview quality loop') and an explicit exclusion ('Isolated layout only — not the live TV'), which routes the agent away from live-render siblings. It does not, however, name a specific alternative tool for live rendering or state prerequisites beyond the required params.

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