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

Annotations already declare readOnlyHint=true, destructiveHint=false, and openWorldHint=false, so the safety profile is covered by structured data. The description adds that this is a legacy alias and that the return shape differs from fetch, but it never says how the shape differs, which is the one behavioral detail an agent would actually need.

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 short sentences, no waste, and the deprecation status plus the recommended alternative are front-loaded. Slightly verbose in restating the domain name twice, but structurally sound.

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 and annotations covering safety, the description supplies the essential deprecation context and the redirect to fetch. The only gap is the unspecified difference in return shape, which would help an agent decide whether the legacy format matters.

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% with a single url parameter already documented as accepting a URL or path (including Japanese text). The description adds nothing about the parameter, so the baseline 3 for a fully documented schema 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 that this is the legacy version of a page-content reader and that it returns the page body like fetch but in a different shape. The verb+resource (read page body) is clear and it is distinguished from the fetch sibling. The phrase about being the 'previously named' function is slightly indirect but overall understandable.

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?

Explicitly tells the agent that this tool is kept only for existing integrations and that new usage should call fetch instead. This is exactly the when-to-use/when-not/alternative guidance the dimension asks for, with the alternative named.

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