把页面渲染成图片

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

With no annotations at all, the description carries the full behavioral burden; it does deliver the key one by promising "不做任何修改" (a non-mutating read). It stops there, saying nothing about the image format, whether the full page or only the viewport is captured, or how the image is returned to the caller.

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 short sentences: the first is the action and the non-mutating guarantee, the second is the usage. Nothing is padded or repeated.

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 one-parameter tool with no annotations and no output schema, the description should say what actually comes back (image as URL? inline data? attachment?). It states only that a rendered image is returned, leaving the return channel unspecified where there is no output schema to fall back on.

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 0%, so pageId is documented nowhere; the description only implies it through "读取页面". The single required parameter has an obvious meaning, which keeps this at minimum viable, but no ID format or scoping semantics are added.

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 uses a concrete verb and resource ("读取页面并返回当前样子的渲染图") and states the output form (a rendered image) rather than just restating the name. It is clear on its own, but it never distinguishes itself from nearby siblings like preview_page or preview_sample, so an agent cannot tell from the text which of these to pick.

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 gives two concrete situations to use it in: reviewing after edits ("修改后复查") and taking a look before an audit ("审计前先看一眼"). That is real situational guidance, but it never rules anything out or names the alternative it replaces, so the boundary with audit_page/preview_page stays implicit.

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