Snapshot

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

No annotations are provided, and the description does not disclose any behavioral traits such as read-only nature, side effects, or state changes. It fails to clarify that this is a read operation (likely safe) and offers no insight into potential pitfalls.

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 short at two sentences, but the first sentence is a fragment and the second is an instruction. It is not structured to clearly convey purpose and usage; it sacrifices clarity for brevity.

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 tool's simplicity (single parameter, no output schema), the description is incomplete. It does not specify the output format (e.g., a list of elements with refs), how refs are derived, or how to use the snapshot with click/type tools. More detail is needed for reliable invocation.

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 has a single 'session' parameter with no description in the schema (schema coverage 0%). The tool description does not explain this parameter at all, leaving the agent to infer its meaning from sibling tools. It fails to compensate for the lack of schema documentation.

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 mentions 'Title, URL, and indexed interactive elements' which gives a sense of what is returned, but the verb 'snapshot' is ambiguous (could be interpreted as a screenshot or a page summary). It implies the tool provides references for interaction but does not clearly state its core function.

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?

No explicit guidance on when to use this tool versus siblings like browser_screenshot or browser_click. The phrase 'Use a ref with click/type' hints at its role but does not provide a clear decision rule or context for invocation.

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