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

Annotations already declare readOnlyHint=true and destructiveHint=false, so the safety profile is covered. The description adds the meaningful context that this is a deprecated alias whose return shape differs from fetch, but it never explains how the format differs or what is returned. Adequate but leaves a real behavioral gap.

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 sentences that carry the key routing message, but the first sentence is dominated by a long parenthetical corporate/site name that reads as noise rather than information. The practical content is front-loaded reasonably, but the opening is not tightly structured.

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 low-risk legacy read alias with no output schema and full schema coverage, the description gives what an agent needs: it is deprecated, it mirrors fetch, and fetch should be preferred. The one omission is a concrete explanation of how the differing return format looks, which matters for callers depending on it.

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 the single url parameter is documented in the schema (URL or path, Japanese allowed). The description adds no parameter syntax beyond that, so the baseline of 3 is correct when the schema does the heavy lifting.

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?

Despite a confusingly embedded site name in the opening quote, the description states clearly that this returns a page body like fetch but in a different form. It distinguishes itself from the sibling fetch by noting the format difference. The core verb+resource is identifiable, though the wrapped corporate title adds noise.

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 explicitly routes the agent: this is the legacy name kept only for those already connected, and 'when using newly, use fetch.' Both the when-to-use (backward compatibility) and the preferred alternative (fetch) are named directly, leaving nothing to inference.

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