Inspect Page

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

Annotations already cover read-only/open-world/non-destructive; the description adds that it does not intentionally modify the target or local filesystem, and that allowPrivateNetwork is deliberately scoped to loopback targets - useful detail. However, idempotence (the annotation idempotentHint is false) is not addressed, and any side effects of network read activity are not covered.

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?

Four crisp sentences: intent, output capsules, the private-network safety cap, safety promise. No filler or repetition; a concrete list of returned elements is valuable rather than boilerplate.

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 gives a reasonable list of returned elements and a security warning, but does not describe the output format/structure of the result, and does not contrast itself with the comparable viewer scan. Given no output schema, the return type is undefined, so one could get by with more contextual build information.

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 schema describes the 5 parameters, but the text label is only explicitly mapped to it, and adds a safety nuance for allowPrivateNetwork. The 0% schema description coverage means the description must carry semantics for all parameters; viewport, includeForms, allowPrivateNetwork, includeAccessibility are not explained anywhere, making them partly guessable.

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 verb ('Read page through outbound network requests and return...') and resource (page elements) with concrete outputs (headings, forms, buttons, links, inputs, role/name selectors, data-testid candidates). It is clearly distinct from scan_url and the Playwright repro/test tools, though it does not explicitly differentiate itself from sibling inspect/read tools.

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?

Usage is implied by the scope (inspect page structure/DOM candidates) and by the conservative network-only fetch, but there is no explicit rule for 'use this instead of scan_url' or any when-not/when-not guidance. Unlike scan_url, it presents concrete candidates for tests, but the exclusivity is not mentioned.

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