browser_read_page

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

Annotations already declare readOnlyHint=true, idempotentHint=true, and destructiveHint=false. The description adds context beyond these: 'Unicode-safe' indicates handling of non-ASCII content, 'next' implies stateful pagination, and 'immutable' reassures that the snapshot does not change. No contradiction with 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?

The description is a single, front-loaded sentence with no redundancy. Every word adds meaning, and the structure is clean and easily scannable.

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 description covers the core action and mentions 'existing immutable snapshot,' but it lacks guidance on how to obtain the snapshot_id, how pagination works with offset/max_chars, and how this tool differs from browser_read. Since an output schema exists, return values are likely covered, but usage context is incomplete.

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%, and the description does not compensate by explaining parameters like snapshot_id, offset, or max_chars. It only hints at pagination with 'next page,' but leaves parameter semantics to the user's inference from names. This falls short for a low-coverage schema.

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 uses a specific verb ('read') with a clear resource ('page from an existing immutable browser snapshot'). It distinguishes itself from siblings like browser_read by specifying 'snapshot' and 'next page', indicating pagination from a saved state.

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 implies usage: read a page from an already-created snapshot, but it does not explicitly state when to prefer this over similar tools like browser_read or site_read_page, nor does it mention any prerequisites beyond having a snapshot. Clear context but no exclusions or alternatives are provided.

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