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

Annotations already declare readOnlyHint=true, openWorldHint=false, and destructiveHint=false, so safety is covered structurally. The description adds genuinely useful context beyond the annotations: this is a deprecated alias kept for backward compatibility, and its output shape differs from fetch's, which is important behavioral information for an agent deciding between the two.

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?

Front-loaded with the legacy framing, then the behavioral difference, then the routing advice. Slightly padded by restating the site name and the 'kept for connected users' clause, but each sentence carries routing or behavioral value.

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?

No output schema exists, and the description says the return format differs from fetch without describing it, which is a minor gap. However, for a deprecated shim whose primary purpose is to redirect agents to fetch, the essential information is present.

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% for the single url parameter, and the schema already explains that URLs or paths (including Japanese) are accepted. The description adds nothing about parameter handling, so the 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?

The description states a specific action (returns the page body) and explicitly frames the tool as the legacy/previous name of a page-reading function, with the site host named. It distinguishes itself from the sibling fetch by noting the return format differs, though it never spells out what that format actually is.

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?

It states plainly when to use it versus the alternative: it is retained only for existing connections, and new usage should call fetch instead. The condition selecting the sibling is unambiguous.

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