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

With no annotations provided, the description carries the full behavioral burden and succeeds. It discloses the coordinate system (top-left origin, y down, pt units), the Chrome/Skia quirk where visible text is rendered as vector outlines with an invisible text layer (marked 'covered':true and color inferred via 'colorFrom':'outline'), and clarifies that paint='clip' represents invisible clipping regions. These non-obvious traits are exactly what an agent needs to interpret output safely.

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?

The description is long but well-structured, with a one-line purpose, bullet lists for content categories, a coordinate note, a quirk note, and a usage recommendation. Each section provides necessary context for a complex extraction tool, so the length is justified, though a bit dense. The core purpose is front-loaded.

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?

Given there is no output schema and no annotations, the description does a strong job of explaining what the tool returns (categories, attributes, coordinate conventions) and common rendering pitfalls. It does not explicitly cover error behavior such as out-of-range pages or corrupted/encrypted files, but the password parameter is already documented in the schema. Overall, an agent has enough to invoke the tool correctly.

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 the baseline is 3. The description mostly repeats what the schema already states about detail ('box' vs 'full') in the usage recommendation ticket, and it adds no meaningful new semantics for path, page, limit, include, password, or precision. The schema is the primary source for parameter meaning.

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 opens with a clear verb and resource: '抽取 PDF 某一页的全部内容' (extract all content of a given PDF page). It then enumerates the three output categories (text, shapes, images) with their specific attributes, making the tool's purpose concrete and easily distinguishable from the sibling pdf_info and pdf_render tools.

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?

The final paragraph gives explicit workflow guidance: extract the whole page first, use detail='box' when shapes are numerous, and combine pdf_extract with pdf_render for focused inspection. This provides clear context and references a sibling tool for a complementary use, though it never explicitly says when to prefer pdf_info over pdf_extract.

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

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

With no annotations, the description carries the burden of behavioral disclosure. It clearly signals read-only behavior ('读取') and, more importantly, specifies the coordinate system (top-left origin, y-down, pt units), which is behavioral information not available in 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 compact sentences with no filler. The output scope and usage context are front-loaded, and the coordinate convention is a purposeful addition rather than redundancy.

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?

There is no output schema, but the description enumerates the return content and gives the coordinate convention, which is essential for interpreting results. It is sufficient for a read-only inspection tool, though exact output field names/types are left unspecified.

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 the schema fully documents path, maxPages, and password. The description adds no parameter-level detail beyond that, matching the baseline for high schema coverage.

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 specific verb ('读取') and resource ('PDF') and enumerates the exact outputs: page count, per-page dimensions/rotation, and metadata. This clearly differentiates it from sibling tools pdf_extract and pdf_render by framing it as document-level inspection.

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 gives a concrete use case: understand structure and decide which pages to process before extraction. It doesn't explicitly say when not to use it or name alternatives, but the stated pre-extraction context is strong enough to guide selection.

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

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

With no annotations provided, the description carries the full behavioral burden and largely succeeds: it discloses the default return mode (base64 image viewable by the agent), the save-alternative (writes file and returns only path info), the region subsetting behavior with the magnifier effect, and the full coordinate convention (top-left origin, y-down, pt units). Minor gaps remain around error behavior (wrong password, invalid page number) and file-overwrite semantics, but the core behavior is clearly disclosed.

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 tightly packed lines: the lead sentence states purpose and use cases, then two bullet-style lines cover return modes and region/coordinate semantics. Every sentence earns its place, key behavior is front-loaded, and there is zero filler or restatement of the schema.

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 9-parameter tool with no annotations and no output schema, the description covers the essentials an agent needs: return formats in both modes, region semantics, and coordinate units, while the schema handles dpi/scale precedence and default values. What's missing is error-behavior context (e.g., behavior on wrong password or out-of-range page) that would fully complete the picture for a tool with two required parameters.

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 the baseline is 3. The description nevertheless adds genuine value beyond the schema: it explains the region+scale synergy as a '放大镜' (magnifying glass), generalizes the coordinate system beyond the region parameter, and defines pt units (1pt=1/72 inch) — none of which the schema states. This justifies one point above baseline.

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 opens with a specific verb+resource+output: '把 PDF 某一页栅格化成图片（PNG/JPEG）' (rasterize a specific PDF page into an image). It further lists concrete use cases — viewing layout, zooming into details, verifying restoration results — which collectively distinguish it from the siblings pdf_info (metadata) and pdf_extract (content extraction) without ambiguity.

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?

Gives explicit use-context through '可用于：整体查看版面、放大局部核对细节、验证还原结果', telling the agent when rendering is the right operation. However, it never names the sibling alternatives (pdf_info/pdf_extract) nor states when NOT to use this tool, so it stops short of the explicit when/when-not/exclusion standard.

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