Tool Linearize

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It does communicate that the output is a progressive-loading, web-optimized version, which is useful. However, it does not explain side effects, such as whether the original file is modified, what the `output` and `overwrite` parameters do semantically, or what happens if output is null.

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 a single concise sentence with no filler, and the key purpose is front-loaded with 'Web 优化'. It is appropriately sized for a simple tool, though the phrasing is slightly vague and could be more explicit about the resource being linearized.

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 tool with 3 parameters, no annotations, and no schema-level parameter descriptions, this description is incomplete. It provides the high-level use case but omits essential operational details like what input path should point to, how output/overwrite interact, and whether the operation is destructive. The sibling names strongly suggest PDF handling, but the description itself does not state this.

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 the description must compensate for parameter meaning, but it only weakly implies an output parameter via '输出'. The required `path` parameter and the `overwrite` behavior are not explained at all, leaving the agent to guess what values and side effects are involved.

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 states a specific behavior: '输出渐进加载版' (outputs a progressive-loading version) and gives the use context: web-optimized, online browsing. It is distinguishable from sibling PDF operations like compress_pdf because it focuses on progressive loading behavior, though it never explicitly names PDF as the resource.

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 description clearly indicates when this tool is appropriate: for publishing files intended to be viewed online, with progressive loading as the goal. It does not mention alternatives or exclusion criteria, but the stated context is specific enough for an agent to select it over general PDF manipulation tools.

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