inspect_page

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

No annotations are supplied, so the description carries the full disclosure burden. It does reveal the payload (accessibility tree, component structure, performance metrics, optional screenshot) and the Playwright dependency, and inspection is inherently read-only, but it says nothing about runtime cost, latency of a headless navigation, failure modes, or whether the call has side effects against the target site.

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?

Two tightly written sentences: the operation is front-loaded in sentence one, and sentence two covers output and the dependency. Nothing is redundant or padded.

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?

For a six-parameter, read-only inspection tool with no output schema and no annotations, the description supplies the missing return-value context (what gets extracted) and a dependency prerequisite. The remaining gap is disambiguation from near-neighbor siblings, but the operational picture is otherwise sufficient.

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% and all six parameters (including enum, ranges, and defaults) are documented in the schema itself. The description only restates that a screenshot is optional, adding no syntax, format, or interaction detail beyond what the schema already provides — the baseline of 3 is correct.

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 gives a specific verb ('Inspect') and resource ('a live web page using a headless browser'), plus an enumeration of what it extracts. It is clear what the tool does, but it never distinguishes itself from plausible siblings such as live_audit, visual_diff, or responsive_preview, which an agent would have to guess between.

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 statement of when to reach for this tool versus the audit/preview siblings, nor any exclusion guidance. The only contextual information is a dependency note ('Requires Playwright (optional dependency)'), which reads more like an environment caveat than usage direction.

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