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

Annotations already declare readOnlyHint/idempotentHint, so 'Free and read-only' is partly redundant, but the description adds genuinely new behavior: large pages are returned in parts, the offset/nextOffset loop, and the requirement to verify version is identical across parts. Nothing contradicts 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?

Front-loaded with the purpose in the first clause, then pagination mechanics in a short second half — every sentence is doing work. Minor waste in restating 'Free and read-only,' which the annotations already declare.

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?

Output schema exists, so return-value documentation is unnecessary; the description nevertheless covers the multi-part read strategy, cursor handling and version-consistency check, which are the only things an agent could get wrong here. Nothing material is missing for a read-only, 3-parameter tool.

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 coverage is 100%, so the baseline is 3; the description goes further by explaining offset as the pagination cursor that completes the read loop ('call again with it as offset and append'). It says nothing about designId/pageKey semantics, but the schema covers those 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?

States a specific verb + resource + scope: 'Read the current HTML of one page on an iter0 canvas, with its version.' That single page/raw-HTML scope distinguishes it from broader siblings like iter0_get_design or iter0_get_canvas_feedback without needing to name them.

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 a clear motivating context ('so you can merge the person's own edits before pushing a revision') that tells the agent when this tool belongs in a workflow. It does not name an alternative or an exclusion, so it stops short of a 5.

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