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

Annotations already declare readOnlyHint/idempotentHint/openWorldHint and destructiveHint=false, so the safety profile is covered. The description adds genuinely useful context beyond that: the return payload is the *full* HTML source (as opposed to a DOM snapshot), which matters since there is no output schema. It omits size/pagination or auth caveats, so it falls short of a 5.

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 tight sentences, zero waste. The scope statement is front-loaded and the disambiguation/alternative follows immediately.

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 single-parameter read tool with no output schema, the description supplies the essentials: what is returned (full HTML source), how it is keyed, and which sibling to use on other platforms. Only minor gaps (source size/truncation, whether a page must be open) remain.

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 coverage is 100% and pageId is already documented as coming from web_navigate; the description only restates '(by pageId)'. With one fully documented parameter, the schema does the heavy lifting and baseline 3 applies.

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?

Names a specific verb+resource (full HTML source of the desktop grid browser page) and identifies the keying parameter (pageId). It explicitly contrasts itself with the sibling webpage_get_dom, so an agent can separate the two without opening either schema.

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 an explicit when-not rule ('Not a device') plus the alternative to use instead ('for a phone or tablet use webpage_get_dom (by udid)'), including that alternative's own keying parameter. The desktop/mobile routing decision is fully spelled out rather than inferred.

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