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

No annotations are provided, so the description carries the full behavioral burden. It discloses the cost ('Costs 1 mcp_call') but says nothing about session behavior, whether an active browser session is required, what happens with the default session, or what form the returned HTML takes. The cost detail is useful but insufficient for a tool with no annotation coverage.

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 two short sentences with no wasted text, and the core action is front-loaded. The cost note is brief and earns its place by adding decision-relevant information.

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?

With no annotations, no output schema, and an undocumented session parameter, the description is too thin to fully support correct invocation. It does not explain session targeting, output shape, or error conditions. For a browser-state-dependent tool, more context is needed.

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?

There is one optional parameter, 'session', with 0% schema description coverage and a default value. The description does not mention the session parameter at all, so it fails to compensate for the missing schema documentation. The agent must infer what 'session' means and when to override it.

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 and resource: 'Return the current page HTML.' That is clear enough to distinguish it from text extraction or screenshot siblings, but it does not explicitly name those alternatives. The purpose is clear without being maximally differentiated.

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?

The description gives no guidance on when to use this tool versus browser_extract_text, browser_screenshot, or other browser tools. It mentions cost, but that does not tell the agent when this HTML retrieval is the right choice. Usage context is left entirely to inference.

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