读取资源内容（按 URL）

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

With no annotations, the description carries the burden and delivers real behavioral detail: automatic UTF-8 correction to avoid mojibake in Chinese text, and base64 output for binary media. It does not mention permissions, truncation side effects beyond maxChars, or error behavior, but the encoding/binary disclosure is genuinely useful beyond the schema.

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, front-loaded with the core action, then the encoding caveat and the binary return behavior. Every sentence conveys distinct information with no filler.

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 read-only fetch tool with no output schema and no annotations, the description covers the return shape (text vs base64) and encoding handling. It leaves error and permission behavior unstated, but the essentials an agent needs to call it correctly are 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%, so url, asBase64, and maxChars are already documented. The description echoes the base64 behavior for binaries but adds no syntax or format detail beyond what the schema states, so the baseline of 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?

States a specific verb and resource (read page resource content by URL) and clarifies scope with a concrete analogy, likening it to opening a file in the DevTools Sources panel. This clearly separates it from siblings like resources_list or network_list, which enumerate rather than fetch content.

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?

Usage is implied through the analogy (fetch a known resource's body) and the schema points to resources_list/network_list as URL sources, but the description itself gives no explicit when-to-use versus alternatives such as network_body or page_dom. An agent must infer the distinction.

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