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

Annotations already declare readOnlyHint=true, openWorldHint=true, and destructiveHint=false, so the safety profile is largely covered. The description adds the authorization/terms constraint, which is useful, but says nothing about return size, what 'current page' means in the session, or whether the HTML is raw or processed.

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?

Three compact sentences, front-loaded with the core action, then usage constraints. No filler. Slightly verbose on the legal/authorization framing relative to the operational content.

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 simple read-only fetch with a single fully-documented parameter and no output schema, the description covers purpose, scope, and ethical constraints. However, it leaves notable gaps: nothing about what the returned HTML looks like or how it relates to 'current page' in a multi-tab session.

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 single sessionId parameter is fully described in the schema (100% coverage) as the connected browser session ID. The description does not elaborate on the parameter or clarify multi-session behavior, so it adds no meaning beyond the schema — baseline 3 is appropriate.

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?

States a specific verb and resource ('Get the HTML content of the current page') with a clear purpose tied to answering the user's request. It implicitly differentiates from siblings like get_elements and take_screenshot by emphasizing HTML content, but never names those alternatives explicitly.

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?

Provides a real usage boundary: only for sites/accounts the user owns or is authorized to use, and explicitly not for crawling or bulk extraction of third-party sites. That is a clear when/when-not, though it doesn't route to a sibling tool for those excluded cases.

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