explore_page

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

With no annotations provided, the description carries the full burden. It usefully discloses that the tool enumerates interactive elements and their predicted effects rather than executing them, implying a read-only reconnaissance role. However, it never explicitily states side-effect behavior, and traits like lazy-content preloading, hidden-element inclusion, or incremental diffs live only in the schema, not the description.

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 and front-loaded with the core concept ('Page map'), which is good. But it ends abruptly with '…', indicating truncation rather than intentional terseness, which is a structural defect for a definition that should be complete.

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?

This is a high-complexity tool (10 optional parameters, several distinct modes: goal, intent, compact, incremental, preload) with no output schema and no annotations. The truncated description leaves the return shape only partially specified, so an agent cannot fully anticipate what explore_page returns in each mode, making the definition incomplete 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?

Schema description coverage is 100%, so the baseline is 3; the tool description adds only the output-structure context (E# refs, action types, effects, F# forms, content) that helps interpret parameters like goal, compact, and intent. It does not go beyond the schema to explain parameter interactions or formats, and several schema descriptions are themselves truncated.

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 states a specific deliverable — a page map of every interactive element with ref (E#), action type, predicted effect, forms (F#), and content — so an agent knows what explore_page produces and roughly what the output looks like. It is not a 5 because it lacks an explicit verb in the description itself and does not differentiate it from siblings like inspect, ax, or read, and the trailing ellipsis truncates the thought.

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?

There is no guidance on when to use explore_page versus the many sibling tools (click, type_text, inspect, screenshot, read, etc.). The only implicit signal is the schema's compact parameter referencing 'old discover_actions', which hints at history but gives no actionable selection criteria or exclusions.

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