browse_session_snapshot

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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the 'Read' claim is consistent and safe. However, the description adds no additional behavioral context beyond the annotations, such as session expiration behavior, error conditions, or the meaning of the captchaPolicy parameter.

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 concise sentence that immediately conveys the tool's purpose without any filler or redundant detail. It is front-loaded and every word contributes to understanding.

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?

Given the presence of a full output schema, extensive annotations (readOnly, openWorld), and complete parameter documentation, the description is sufficient for basic understanding. It does not explain non-obvious aspects like CAPTCHA handling, but those are covered in the schema, so this is acceptable for a read-only snapshot 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?

The input schema provides 100% parameter coverage, including descriptions for all five parameters, so the schema carries the full burden. The description adds no extra meaning to the parameters, therefore the baseline of 3 applies.

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 clearly states the action (read) and the resource (current state of an existing browser session), making it distinct from session creation or navigation tools. It does not explicitly name sibling alternatives, but the phrase 'existing browser session' differentiates it from non-session snapshots like browse_snapshot.

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 is for an already-started session, but it provides no explicit when-to-use guidance or exclusions compared to sibling tools. The context signal that a sessionId is required is present in the schema, not the description, so the guidance remains only implicit.

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